Changing aws_ssm_parameter.overwrite trigger a resource update

[kid]

Terraform Version

Terraform v0.10.6

Affected Resource(s)

• aws_ssm_parameter

Expected Behavior

Changing the overwrite parameter from true to false or vice versa should not trigger an update

Actual Behavior

Changing overwrite from true to false trigger an update which then fails because the value can not be updated with overwrite set to false

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. Create a aws_ssm_parameter with overwrite set to true
2. Run terraform apply
3. change overwrite set to false
4. Run terraform apply again

References

Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:

• Not possible to allow SSM Parameter overwrites only for updates (and not creates) #1481
• Allow parameters to follow standard lifecycle rules #1556

[ernoaapa]

Temporary workaround:

  lifecycle {
    ignore_changes  = ["overwrite"]
  }

[bflad]

Is this still an issue on v1.11.0 of the AWS provider? Thanks!

[bflad]

It looks like this functionality made it in via #1520, which was previously released in version 1.11.0 of the AWS provider and has been available in all releases since. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

[jleclanche]

@bflad This is a bug report on the added functionality, it's more recent than the PR.

[bflad]

The PR in question was merged in March and this issue is from January. I'll reopen it though.

[avoidik]

Currently we're affected by the overwrite edge-case issue. We had initially created SSM value with Terraform, then we have been rewriting the same SSM key with another automation script. In this case subsequent Terraform provisioning leads to the error below

* aws_ssm_parameter.secret: error creating SSM parameter: ParameterAlreadyExists: The parameter already exists. To overwrite this value, set the overwrite option in the request to true.

Lifecycle rule hasn't helped us much

  lifecycle {
    ignore_changes = ["value", "overwrite"]
  }

[rmclaughlin-nelnet]

Is there an update on this? I am running into the same issue. I am trying to move control of SSM parameters to Terriform, but have them updated through another process. This does not seem possible currently because Terraform always complains ParameterAlreadyExists: The parameter already exists. To overwrite this value, set the overwrite option in the request to true.

[beanaroo]

We'd like to switch to overwrite = false to prevent potential conflicting parameters but this is getting in the way.

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[avoidik]

This issue hasn't been resolved

[github-actions]

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.