You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The user should be able to create, read, update, and delete (CRUD) environments variables for their account but also specify a target project for each environment variable.
Proposal
In this first MVC (minimum viable change), we can do the following:
Introduce a dedicated page for creating, reading, updating, and deleting environment variables.
(Optional) Rename Environment Variables to Variables to make it friendlier to the user but also allow future features like supporting other types (see Support multiline environment variables #2058), etc.
Show a modal dialog to prompt the user for a variable key, value, and project scope.
Problem to solve
Currently, Environment Variables are mixed with other user settings like API Tokens, Notifications, etc.
This is part of #3300. 🍕
User Experience goal
The user should be able to create, read, update, and delete (CRUD) environments variables for their account but also specify a target project for each environment variable.
Proposal
In this first MVC (minimum viable change), we can do the following:
Components involved:
Future steps
Designs
For spacing guidelines, see similar patterns in #3399.
See also design specs.
Documentation
No documentation changes are needed for this first iteration.
The text was updated successfully, but these errors were encountered: