Environment-specific variables
Description
Developers and Ops should be able to specify different values for secret (and not-so-secret) variables, and tie them to environments. For example, doing a deploy to Heroku might need an app name, which you could specify by $HEROKU_APP_NAME, but that name would be different in staging and production.
Proposal
- Add a scope to variables so that you could say var A applies to environment B.
- Support wildcards, so you could say that some deploy variable applies to
review/*and all review apps would get the variable automatically. - Default scope is
*.