Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Per-environment configs #3

Open
rsyring opened this issue Mar 3, 2024 · 0 comments
Open

Per-environment configs #3

rsyring opened this issue Mar 3, 2024 · 0 comments

Comments

@rsyring
Copy link
Member

rsyring commented Mar 3, 2024

  • Need to be able to specify different config for different environments
  • Some type of list of used/approved environments. If you have the config for each, you can use that. But then for the devs, there's going to be different environment names (e.g. rsyring.meld). Maybe the environment name in that case is always "dev" but a different ident is used in the config for the special case of "dev" environment so that any objects created in AWS have the dev's preferred ident (e.g. rsyring.meld).
  • A simple app with no config for the different environs could probably give a static list of expected environment names.
  • Maybe rename "environment" in this context to "profile" to avoid overloading "environment"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant