-
-
Notifications
You must be signed in to change notification settings - Fork 222
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
Feature Request: Manage Project Keys with CLI #2030
Comments
@souredoutlook, to clarify, the feature you are requesting here is a new Sentry CLI command that would create a new DSN for a given project? |
Important to note that outcome the customer wants to achieve: Disable old releases of their app. |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Hey @bruno-garcia , do you know if there's an ETA on the Remote Config tool? 😃 |
Being able to manage project keys with the CLI will enable devs that are already using the CLI in their project release management workflow to programattically use a new DSN in production releases. This is an important part of some mobile dev workflows as it allows them to manage seperate releases' ingestion on the Sentry server more easily.
See this comment for more details: getsentry/sentry#68059 (comment)
cc @stephanie-anderson
The text was updated successfully, but these errors were encountered: