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

aws_ecs_service InvalidParameterException: Creation of service was not idempotent #16635

Closed
simoneroselli opened this issue Nov 13, 2017 · 2 comments

Comments

@simoneroselli
Copy link

simoneroselli commented Nov 13, 2017

Terraform Version

v0.10.8

Hi,

terraform is failing on modify the "placement strategy" for ECS/Service resources. Since such value can only be set at Service creation time, the expected beahviour would be "destroy 1, add 1", like the terraform plan correctly reports. However on terraform apply it fails.

Fail Output

Error: Error applying plan:

1 error(s) occurred:

  • module.<my_module>.aws_ecs_service.<my_resource_name>: 1 error(s) occurred:

  • aws_ecs_service.main: InvalidParameterException: Creation of service was not idempotent.
    status code: 400, request id: xxxxxxxxxxxxxxxx "..."

Expected Behavior

destroy service, add service.

Actual Behavior

Failure of terraform without modification.

Steps to Reproduce

  1. Define a ECS/service with a placement strategy and apply
  2. Change the placement strategy values to something else
  3. terraform plan
    Plan: 1 to add, 0 to change, 1 to destroy.
  4. terraform apply
    InvalidParameterException: Creation of service was not idempotent
@hashibot
Copy link
Contributor

This issue has been automatically migrated to hashicorp/terraform-provider-aws#2283 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to this issue and let us know.

@ghost
Copy link

ghost commented Apr 6, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants