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

Make setting params easier based on stack-args #92

Open
jpb opened this issue Mar 8, 2018 · 4 comments
Open

Make setting params easier based on stack-args #92

jpb opened this issue Mar 8, 2018 · 4 comments

Comments

@jpb
Copy link
Contributor

jpb commented Mar 8, 2018

Given a stack args like:

$imports:
  params: ssm-path:/path/to/params/

...
Parameters:
  ImageId: !$ params.ImageId

allow something like this to work:

iidy param set stack-args.yaml params.ImageId ami-000000

where params is the $imports variable name that points to a SSM parameter path. This would set /path/to/params/ImageId to ami-000000.

This should work with iidy param --environment ... or other imports that are used to produce the ssm-path.

Related, it would be nice to have iidy param update that fails if it isn't overwriting a parameter (the opposite of iidy set without --overwrite). This, in conjunction with the above, would prevent users from setting the wrong parameter (eg. setting the wrong path or the correct path in the wrong region).

@tavisrudd
Copy link
Collaborator

Any thoughts on how we'd deal with ad-hoc naming of the $imports or import of multiple ssm-paths (app-specific, shared, etc.)?

@jpb
Copy link
Contributor Author

jpb commented Mar 8, 2018

params isn't a special identifier - it could be called anything:

$imports:
  cats: ssm-path:/cats/
  dogs: ssm-path:/dogs/

...
Parameters:
  ImageId: !$ cats.ImageId
iidy param set stack-args.yaml cats.ImageId ami-000000

@tavisrudd
Copy link
Collaborator

@jpb are you still interested in this?

@tavisrudd
Copy link
Collaborator

Shall we close this?

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

2 participants