-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Control plane logs #235
Control plane logs #235
Conversation
✅ Deploy Preview for shiny-alfajores-ede8d8 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
6. Paste `<<LOG-SHIPPING-TOKEN>>` into the content text box. | ||
7. Click **Create**. | ||
|
||
{@include: ../../_include/log-shipping/log-shipping-token.html} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The placeholder will probably look ok in the app, but it looks a little funny in the public docs, because it looks just like this <> without any explanation that this is a logzio log shipping token.
spec: | ||
logging: | ||
logzio: | ||
credentials: //secret/<<LOG-SHIPPING-TOKEN>> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this right? If we stored the shipping token as a secret, I don't think that you're expected to write it explicitly here, I would assume that you'd need to write the name of the opaque secret you created in the first step.
Can you please check this part?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct, it's the secret's name that we need to specify, not the token!
No description provided.