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

Constants Parameter Resolver #110

Open
patrobinson opened this issue May 10, 2016 · 2 comments
Open

Constants Parameter Resolver #110

patrobinson opened this issue May 10, 2016 · 2 comments
Assignees

Comments

@patrobinson
Copy link
Contributor

We find ourselves putting account IDs in parameter files a few times and this opens a potential enhancement.

We could have a Constants parameter resolver that works like so:

permitted_account:
  constant: account_id/my_awesome_other_account

Where this looks up another YAML file in constants/account_id.yml:

my_awesome_other_account: 0123456789012
@patrobinson
Copy link
Contributor Author

The Latest AMI resolver also accepts an account ID as input, so there would also be benefit in supporting nested parameter resolvers, but this would be rather difficult to implement.

@simpsora
Copy link
Contributor

I'd be interested to see how secrets could work here -- I can see a need to share a secret with multiple stacks, and since we already have secret support (via dotgpg), making it usable here would be nice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants