Closed jpb closed 2 months ago
Any thoughts on how we'd deal with ad-hoc naming of the $imports
or import of multiple ssm-paths
(app-specific, shared, etc.)?
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
@jpb are you still interested in this?
Shall we close this?
Given a stack args like:
allow something like this to work:
where
params
is the$imports
variable name that points to a SSM parameter path. This would set/path/to/params/ImageId
toami-000000
.This should work with
iidy param --environment ...
or other imports that are used to produce thessm-path
.Related, it would be nice to have
iidy param update
that fails if it isn't overwriting a parameter (the opposite ofiidy 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).