Is your feature request related to a problem? Please describe.
It can get hard to remember what exactly a secret is used for. For example, within some of the frontend projects, there are up to 4 Sentry secrets. Some are for node/express (server side), some are for browser side, and it can be hard to keep track. In addition, it's easier to clean up
secrets when we know their purpose.
Obviously this is all contingent on someone actually filling them out. But feature requests require a bit of optimism regardless :)
Describe the solution you'd like
A custom text(area) field for each secret. Beginning few words could be shown in the table, perhaps, but whole thing would be shown and editable when clicking on a secret.
Describe alternatives you've considered
Alternatives include - Just grep for the secret and look at code to see how it's used, which can work, but can also be a rabbit hole
Is your feature request related to a problem? Please describe.
It can get hard to remember what exactly a secret is used for. For example, within some of the frontend projects, there are up to 4 Sentry secrets. Some are for node/express (server side), some are for browser side, and it can be hard to keep track. In addition, it's easier to clean up
secrets when we know their purpose.
Obviously this is all contingent on someone actually filling them out. But feature requests require a bit of optimism regardless :)
Describe the solution you'd like
A custom text(area) field for each secret. Beginning few words could be shown in the table, perhaps, but whole thing would be shown and editable when clicking on a secret.
Describe alternatives you've considered
Alternatives include - Just
grepfor the secret and look at code to see how it's used, which can work, but can also be a rabbit hole