Open t0yv0 opened 4 months ago
Voting for Prioritization
Volunteering to Work on This Issue
I spent a good bit of time bumping up against this bug - during the apply
, we tracked the actual API calls to AWS and had the following 4 calls executed:
1. 2024-09-09T20:16:57.046Z - PutRestApi
2. 2024-09-09T20:17:12.005Z - CreateDeployment
3. 2024-09-09T20:17:19.403Z - UpdateStage
4. 2024-09-09T20:17:19.945Z - UpdateRestApi
The first PutRestApi
properly applied the policy, but moments later, the UpdateRestApi
call came in and reverted the policy to some old version.
I'm facing the same issue here. Do we have any updates on that?
Terraform Core Version
1.6.3
AWS Provider Version
5.9.0
Affected Resource(s)
Expected Behavior
When updating x-amazon-apigateway-policy inside body, expect the policy output and the cloud state to get updated accordingly.
Actual Behavior
When updating x-amazon-apigateway-policy inside body, body gets updated but the cloud state and policy are retained from the previous state.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
infra.tf:
policy.json:
policy2.json is the same except
aws:SourceIp: "10.0.0.3"
is replaced withaws:SourceIp: "10.0.0.4"
.Steps to Reproduce
Observe in
terraform state show aws_api_gateway_rest_api.example
:Note that
"aws:SourceIp" = "10.0.0.3"
did not get updated.Debug Output
N/A
Panic Output
N/A
Important Factoids
N/A
References
N/A
Would you like to implement a fix?
None