-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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_apigatewayv2_integration" updates "passthrough_behavior" on every terraform plan #13893
Comments
Oops, sorry for the duplicate. Missed that when searching existing issues. :( |
@lxg Actually, it's not a duplicate as the linked PR didn't have an explicit issue it was closing. |
Seeing the same issue - not defining api_gatewap.tf
terraform.tfstate
Planned changes
|
Closed via #13062. |
This has been released in version 3.0.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Terraform Version
Terraform v0.12.26
Affected Resource(s)
Terraform Configuration Files
Here’s the relevant code of our config:
Here’s the output of
terraform plan
Expected Behavior
terraform plan
should not schedule any changes. Especially aspassthrough_behavior = "WHEN_NO_MATCH"
is the default anyway. Removing the explicit setting in the config yields the same behaviour.Actual Behavior
This keeps happening after every terraform apply, so there is never a “consistent” state.
The text was updated successfully, but these errors were encountered: