Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Our org's data region is EU (de.sentry.io), but org auth tokens created in the org embed sentry.io, and
sentry-cli/@sentry-vite-plugin uses the token's region over both SENTRY_URL and the url option. How do we get an EU-region org token, or force EU upload? Asking Seer it tells me This is a known bug/limitation: org auth tokens created via *.sentry.io embed sentry.io as their region URL, and sentry-cli/@sentry/vite-plugin trust the token's embedded region over any config override. There's no UI workaround on linkxg.sentry.io.
Expected Result
Generate an org token which resolves to de.sentry.io
Actual Result
org token resolves to sentry.io and ignores SENTRY_URL and url: params
Product Area
Settings - Developer Settings
Link
No response
DSN
https://b20d15a72990ed54517fd5e3ef8ae283@o4511468986302464.ingest.de.sentry.io/4511468992004176
Version
No response
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Our org's data region is EU (de.sentry.io), but org auth tokens created in the org embed sentry.io, and
sentry-cli/@sentry-vite-plugin uses the token's region over both SENTRY_URL and the url option. How do we get an EU-region org token, or force EU upload? Asking Seer it tells me This is a known bug/limitation: org auth tokens created via *.sentry.io embed sentry.io as their region URL, and sentry-cli/@sentry/vite-plugin trust the token's embedded region over any config override. There's no UI workaround on linkxg.sentry.io.
Expected Result
Generate an org token which resolves to de.sentry.io
Actual Result
org token resolves to sentry.io and ignores SENTRY_URL and url: params
Product Area
Settings - Developer Settings
Link
No response
DSN
https://b20d15a72990ed54517fd5e3ef8ae283@o4511468986302464.ingest.de.sentry.io/4511468992004176
Version
No response