Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Terraform Version
Terraform v0.12.26
- provider.aws v2.67.0
- provider.local v1.4.0
- provider.null v2.1.2
- provider.random v2.2.1
- provider.template v2.1.2
Affected Resource(s)
- aws_apigatewayv2_integration
Terraform Configuration Files
Here’s the relevant code of our config:
resource "aws_apigatewayv2_integration" "services_gateway" {
api_id = aws_apigatewayv2_api.services_gateway.id
integration_type = "HTTP_PROXY"
connection_type = "VPC_LINK"
integration_method = "ANY"
passthrough_behavior = "WHEN_NO_MATCH"
connection_id = aws_apigatewayv2_vpc_link.services_gateway.id
integration_uri = module.tf_application_load_balancer.load_balancer_listener_arn
}
Here’s the output of terraform plan
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
# aws_apigatewayv2_integration.services_gateway will be updated in-place
~ resource "aws_apigatewayv2_integration" "services_gateway" {
api_id = "…"
connection_id = "…"
connection_type = "VPC_LINK"
id = "…"
integration_method = "ANY"
integration_type = "HTTP_PROXY"
integration_uri = "arn:aws:elasticloadbalancing:…"
+ passthrough_behavior = "WHEN_NO_MATCH"
payload_format_version = "1.0"
request_templates = {}
timeout_milliseconds = 29000
}
Plan: 0 to add, 1 to change, 0 to destroy.
Expected Behavior
terraform plan should not schedule any changes. Especially as passthrough_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.
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 planExpected Behavior
terraform planshould 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.