feat(docs) Add server metadata to files endpoints #82159
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Several of our files endpoints require usage of the region domains instead of sentry.io or slug.sentry.io. Having the server context defined in these endpoints will enable us to generate better example code in the docs. Refs #81232
github-actions
bot
added
the
Scope: Frontend
JoshFerge
approved these changes
Dec 16, 2024
We shouldn't need the us/de list if we also have the templated region domain as well.
github-actions
bot
added
the
Scope: Backend
Contributor
|
🚨 Warning: This pull request contains Frontend and Backend changes! It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently. Have questions? Please ask in the |
evanh
pushed a commit
that referenced
this pull request
Dec 17, 2024
Several of our files endpoints require usage of the region domains instead of sentry.io or slug.sentry.io. Having the server context defined in these endpoints will enable us to generate better example code in the docs. Refs #81232
markstory
added a commit
to getsentry/sentry-docs
that referenced
this pull request
Dec 17, 2024
Some of our endpoints require customers to use region domains in order to have APIs work correctly across DE and US regions. I've already updated those endpoints in getsentry/sentry#82159. Refs getsentry/sentry#81232
6 tasks
markstory
added a commit
to getsentry/sentry-docs
that referenced
this pull request
Dec 17, 2024
Some of our endpoints require customers to use region domains in order to have APIs work correctly across DE and US regions. I've already updated those endpoints in getsentry/sentry#82159. Refs getsentry/sentry#81232
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Several of our files endpoints require usage of the region domains instead of sentry.io or slug.sentry.io. Having the server context defined in these endpoints will enable us to generate better example code in the docs.
Refs #81232