This is related to #33853 however I would consider this bug even higher priority since it is leading to user thinking resources are deleted and not being tracked in state file anymore.
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.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Terraform Core Version
1.5.2
AWS Provider Version
5.20.0
Affected Resource(s)
Expected Behavior
Terraform should acknowledge error from AWS API and report to user that resource couldn't be destroyed.
Actual Behavior
Terraform reported that resource was successfully destroyed and removed it from state file.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
Run the above code as is. Then comment out current version of SG rule and uncomment the other one to change the protocol & ports.
Debug Output
aws_sgrevoke_debug.txt
Panic Output
No response
Important Factoids
No response
References
This is related to #33853 however I would consider this bug even higher priority since it is leading to user thinking resources are deleted and not being tracked in state file anymore.
Would you like to implement a fix?
No