-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Use org auth token in JS and Sentry CLI docs #7714
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -28,7 +28,7 @@ sentry-cli --url https://myserver.invalid/ login | |||
|
|||
## To authenticate manually: | |||
|
|||
Visit your [auth token user settings page](https://sentry.io/settings/account/api/auth-tokens/) and create or copy an existing token. Then either: | |||
Visit the [Organization Auth Token Settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/auth-tokens/) and create a new token or copy an existing one. Then either: |
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.
m: You can't copy an existing one anymore 😅 so:
Visit the [Organization Auth Token Settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/auth-tokens/) and create a new token or copy an existing one. Then either: | |
Visit the [Organization Auth Token Settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/auth-tokens/) and create a new token. Then either: |
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.
Ah right
SENTRY_AUTH_TOKEN=___ORG_AUTH_TOKEN___ | ||
SENTRY_ORG=___ORG_SLUG___ | ||
SENTRY_PROJECT=___PROJECT_SLUG___ |
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.
we should move always move this below the org/project slug, as in the UI they are kind of coupled together - selecting the org/project influences where you create the token for. So IMHO it is a better flow to always make this:
SENTRY_AUTH_TOKEN=___ORG_AUTH_TOKEN___ | |
SENTRY_ORG=___ORG_SLUG___ | |
SENTRY_PROJECT=___PROJECT_SLUG___ | |
SENTRY_ORG=___ORG_SLUG___ | |
SENTRY_PROJECT=___PROJECT_SLUG___ | |
SENTRY_AUTH_TOKEN=___ORG_AUTH_TOKEN___ |
Co-authored-by: Francesco Novy <[email protected]>
Visit the [auth token user settings page](https://sentry.io/settings/account/api/auth-tokens/) to find your auth tokens. | ||
|
||
</Note> | ||
<OrgAuthTokenNote /> | ||
|
||
<SignInNote /> |
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.
<SignInNote /> |
OrgAuthTokenNote is kind of a more detailed version of SignInNote, so when we show this we can skip the sign in note!
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 sign in note needs to come before every instance where we use ___ORG_SLUG___
or ___PROJECT_SLUG___
.
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.
They describe two different things
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.
Hmm, I guess it's true... but - it's a bit weird to have two of these note boxes over each other that both show similar-but-not-quite-the-same info 🤔
What about just updating the not-signed-in test of the <OrgAuthTokenNote>
from:
You can manually create an Auth Token or sign in to create a token directly from the docs.
to something like
You can manually create an Auth Token or sign in to create a token directly from the docs. Once you sign in, you will be able to select your personal config from a dropdown.
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.
With #7716 we can make this all a bit more cleaner
@@ -197,7 +197,7 @@ You can set them as environment variables, for example in a `.env` file: | |||
|
|||
- `SENTRY_ORG` your Sentry org slug | |||
- `SENTRY_PROJECT` your Sentry project slug | |||
- `SENTRY_AUTH_TOKEN` your Sentry auth token | |||
- `SENTRY_AUTH_TOKEN` your Sentry auth token (can be obtained from https://sentry.io/orgredirect/organizations/:orgslug/settings/auth-tokens/) |
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.
- `SENTRY_AUTH_TOKEN` your Sentry auth token (can be obtained from https://sentry.io/orgredirect/organizations/:orgslug/settings/auth-tokens/) | |
- `SENTRY_AUTH_TOKEN` your Sentry auth token (can be obtained from [your Organization Settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/auth-tokens/)) |
Maybe something like this? The link is kind of ugly...
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.
LGTM
src/docs/product/sentry-basics/integrate-frontend/configure-scms.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platforms/javascript/common/sourcemaps/uploading/angular-nx.mdx
Outdated
Show resolved
Hide resolved
src/platforms/javascript/common/sourcemaps/uploading/angular-webpack.mdx
Outdated
Show resolved
Hide resolved
@@ -129,7 +129,7 @@ module.exports = { | |||
org: "___ORG_SLUG___", | |||
project: "___PROJECT_SLUG___", | |||
|
|||
// Auth tokens can be obtained from https://sentry.io/settings/account/api/auth-tokens/ | |||
// Auth tokens can be obtained from the your User Settings | |||
// and need `project:releases` and `org:read` scopes |
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.
Whats the reason we are not replacing this with org tokens here?
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.
This is in the legacy docs. People here may use a self hosted version that is not yet compatible with org auth tokens.
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.
ah, makes sense! 👍
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.
great work!
Co-authored-by: Liza Mock <[email protected]>
Updates the docs for JavaScript and Sentry CLI source maps upload to use org auth tokens when applicable.
Closes getsentry/team-webplatform-meta#62