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

Stack createion fails when using --parameters-override #122

Closed
ghost opened this issue Apr 12, 2017 · 3 comments
Closed

Stack createion fails when using --parameters-override #122

ghost opened this issue Apr 12, 2017 · 3 comments

Comments

@ghost
Copy link

ghost commented Apr 12, 2017

When using the cloudformation deploy command with --parameter-overrides, stack creation fails with the following message -

An error occurred (ValidationError) when calling the CreateChangeSet operation: Cannot specify UsePreviousValue on Parameters when ChangeSetType is CREATE

I'm using the following command -

aws cloudformation deploy \
    --template-file template.yaml \
    --stack-name "TestStack" \
    --region eu-west-1 \
    --parameter-overrides \
        Environment="BVT"
        S3BucketName="bvt-dump-payload-test-eu-west-1"

My template contains the following Parameters definition -

Parameters:
  Environment:
    Type: String
    Description: The environment that is being deployed to, such as BVT, UAT, etc.
  S3BucketName:
    Type: String
    Description: The S3 Bucket to which the Lambda Function will output payloads.

I had found an issue on here suggesting tha tyou needed to declare a default value in the template, but that also produces the above error.

@digitalfiz
Copy link

If your paste is correct then you missed a \ after Environment="BVT" which would leave the S3BucketName="bvt-dump-payload-test-eu-west-1" out of the command. It would actually run S3BucketName="bvt-dump-payload-test-eu-west-1" as a separate command.

@ghost
Copy link
Author

ghost commented Apr 12, 2017

Ah, that is indeed the issue!

Fooled by the red herring returned by AWS, I assumed the command was correct and didn't consider it as the source of the problem.

Thanks for posting.

@ghost ghost closed this as completed Apr 12, 2017
@digitalfiz
Copy link

np!

hawflau added a commit that referenced this issue Apr 6, 2022
* feat: Support for Lambda URL (#86)

* feat: changed CorsConfig property to Cors (#89)

* feat: add list of "unreleased" properties (#91)

This change hides the unreleased properties from the "Globals" error message

* Lambda URL integ test (#94)

* remove functionUrlConfig from the unrelease properties (#97)

* remove functionUrlConfig from the unrelease properties

* updates

* Function Url new changes  (#109)

* update to Function Url

* first update

* reverted to support autopublishing and added validation for AuthType values

* adding Integration test

* fix: fix paths IF intrinsic bug (#107)

* fix: fix paths IF intrinsic bug

* missed bit of code

* add NoValue tests

* review feedback and refactoring

* naming fix

* review feedback naming and comments

* add missing test + add extra check for api key on tests

* integration test updated (#122)

Co-authored-by: jonife <79116465+jonife@users.noreply.github.com>
Co-authored-by: Renato Valenzuela <37676028+valerena@users.noreply.github.com>
Co-authored-by: Ruperto Torres <86501267+torresxb1@users.noreply.github.com>
This issue was closed.
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

1 participant