Repository navigation

Per-environment configs #3

Open

opened

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"

calebsyring commented on Dec 3, 2025
calebsyring
on Dec 3, 2025
Contributor
Wishlist:

support for multiple project-orgs (if I want my mu lambda to exist in multiple aws accounts/environments)

policy_arns that are different per project-org and per dev (would need to depend on environment variables somewhat)

Ideally I could also specify which mu env/namespace to use via environment variable if that's not supported already.
calebsyring commented on Dec 3, 2025
calebsyring
on Dec 3, 2025
Contributor
Regarding terminology, I propose:

aws_account (for aws account)

mu_namespace (for differentiating/namespacing mu resources within accounts)
rsyring commented on Dec 9, 2025
rsyring
on Dec 9, 2025
MemberAuthor
Did this get resolved with #27?
calebsyring commented on Dec 9, 2025
calebsyring
on Dec 9, 2025
Contributor
I didn't close this issue because I think it's a little broader in scope and has some conveniences in mind, but #27 covers the core of this.

to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

Labels

No labels

No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests