Problem or Use Case
It's quite often the case that the user will want to add a variable to all environments if it's missing, but if it's already there then read from the specific environment.
Take for example DATABASE_URL and you are building locally.
- If that variable has been set for prod and dev, you'll want to read the
development DATABASE_URL
- If you are setting up the database for the very first time, you'll probably want to store that variable on the repository level to have it used for all environments
Proposed Solution
There's a couple of ways to solve this. Perhaps, have a read environment, and write environment? Perhaps if the variable isn't set at all for any environment then default to the repo level. Perhaps add an option the store at repo level if missing.
Think through pros and cons of each option before implementing
Problem or Use Case
It's quite often the case that the user will want to add a variable to all environments if it's missing, but if it's already there then read from the specific environment.
Take for example
DATABASE_URLand you are building locally.developmentDATABASE_URLProposed Solution
There's a couple of ways to solve this. Perhaps, have a read environment, and write environment? Perhaps if the variable isn't set at all for any environment then default to the repo level. Perhaps add an option the store at repo level if missing.
Think through pros and cons of each option before implementing