[Bug]: Removing existing invocation_http_parameters block in aws_cloudwatch_event_connection creates permanent diff #37814
Labels
bug
Addresses a defect in current functionality.
service/events
Issues and PRs that pertain to the events service.
Terraform Core Version
1.8.4
AWS Provider Version
5.52.0
Affected Resource(s)
aws_cloudwatch_event_connection
Expected Behavior
Here is a sequence of events:
invocation_http_parameters
present and run terraform applyinvocation_http_parameters
and run terraform apply.Actual Behavior
After step 2 any terraform apply will report that it attempts to remove
invocation_http_parameters
block from config, producing permanent diffRelevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
invocation_http_parameters
blockinvocation_http_parameters
block and run terraform apply againinvocation_http_parameters
blockDebug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: