Support in parameter files in --parameter-overrides

[digitalfiz]

As requested by @sanathkr over a year ago in aws/serverless-application-model#111 I am submitted a request to support parameter files in the --parameter-overrides flag.

Sorry I never got any notifications for some reason...

[justnance]

@digitalfiz, Thank you for following up. We are investigating this request and so far it appears to be a reasonable feature request and have changed the label as such. Thanks.

cc: @sanathkr

[atkretsch]

Don't know if this should be a separate feature request, but it would be great if --parameter-overrides supported YAML-formatted files.

[linusguan]

This feature would be awesome, we are still hacking it using a file with key=value

[adamfortuno]

It's Agree. Feature would be helpful.

[anabadce]

This is how I solved this for now:

STACK=myStack
TEMPLATE=stack.yaml
PARAMETERS=config1.json

PROPERTIES=$(jq -r '.[] | "\(.ParameterKey)=\(.ParameterValue)"' ./$PARAMETERS)

aws cloudformation deploy \
--stack-name $STACK \
--template-file "./$TEMPLATE" \
--parameter-overrides $(echo $PROPERTIES)

• Using jq to easy convert from json to key=value
• Config file is json because that is what aws cloudformation create-change-set uses for example
• Config looks like this:

[
  {
    "ParameterKey": "Environment",
    "ParameterValue": "dev"
  }
]

[kenlju]

We had some problem when one of the parameter values contained a cron expression cron(0 * * * ? *). Then the shell would expand the * to the filenames in the directory.

bash-3.2$ ls 
testfile
bash-3.2$ CR="cron(0 * * * ? *)"
bash-3.2$ echo $CR
cron(0 testfile testfile testfile ? *)
bash-3.2$ echo "$CR"
cron(0 * * * ? *)

[tim-finnigan]

In CLI v2 there is documented support for using a JSON file with --parameter-overrides: https://awscli.amazonaws.com/v2/documentation/api/latest/reference/cloudformation/deploy/index.html#examples

But there is another open feature request to use a parameter file in YAML format (as @atkretsch requested in this comment): #5473

Closing this issue as the JSON file option is available. Please refer to #5473 for updates on the request for YAML file support.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.