If you accidentally leak an API key, or for some other reason you want to change it, you can't.
Currently, you have to create a new Project, and switch your Jobs to using that. This isn't actually difficult to do but it's not ideal and has the major drawback of your Run history being in two places.
Solution
- Add the ability to regenerate each of the API keys in the UI
- We need to show an appropriate warning, as this will temporarily break any live Jobs until the new API key has been set in the relevant env vars.
Possibly we should ask the user to type the name of the project into a text field and then press a button to confirm.
TRI-1415
If you accidentally leak an API key, or for some other reason you want to change it, you can't.
Currently, you have to create a new Project, and switch your Jobs to using that. This isn't actually difficult to do but it's not ideal and has the major drawback of your Run history being in two places.
Solution
Possibly we should ask the user to type the name of the project into a text field and then press a button to confirm.
TRI-1415