Closed amcinnes closed 6 years ago
Oh, I know what the issue is -- I used a parameters.json file that I was previously using with some other deployment tool, and it had some "special" things in it rather than the usual ParameterKey and ParameterValue fields.
Does this still need attention, @amcinnes?
If so, can you provide a (minimal) input file that demonstrates the problem, and a suggestion about what a better error message might be?
Okay, here's a minimal template (template.json
):
{
"Parameters": {
"woop": {
"Type": "String"
}
},
"Resources": {
"Topic": {
"Type": "AWS::SNS::Topic"
}
}
}
and a minimal parameters file which causes the problem (parameters.json
):
[
{
"ParameterKey": "woop",
"ParameterValue": "pie",
"StackName": "spam"
}
]
and the command to deploy it:
docker run --rm \
-v `pwd`:/cwd \
-e AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY -e AWS_SESSION_TOKEN \
-e AWS_DEFAULT_REGION=ap-southeast-2 \
realestate/stackup:latest angus-test-stack up -t template.json -p parameters.json
The problem is that I have this StackName
key in parameters.json
which shouldn't be there. Without that line, the stack deploys successfully.
With that StackName
line there, I would ideally see an error message like `Invalid key "StackName" in parameters file" instead of a Ruby stacktrace.
Got it. Thanks.
I'm getting this error:
when running this command:
I'm not sure exactly what I'm doing wrong, and the error message certainly doesn't make it obvious.