Closed chenian closed 1 month ago
Voting for Prioritization
Volunteering to Work on This Issue
Hey @chenian 👋 Thank you for taking the time to raise this! I can't quite tell for certain with the information we have, but I suspect that when you're making the modification in the AWS console, it's causing the rule's ID to change, so Terraform sees it as having "disappeared" and attempts to recreate it. This may be a case where you need to import the resource, but it may also help if you can provide debug logging for the run after your manual modification in the console (redacted as needed).
Hey @chenian 👋 The enhancement request that you linked to has since been merged, which should resolve this altogether. With that and that we haven't heard back in mind, I'm going to close this issue. Please do let us know if you run into any other unexpected behavior!
[!WARNING] This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.
Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Terraform Core Version
1.7.1
AWS Provider Version
5.44.0
Affected Resource(s)
aws_route53_resolver_firewall_rule
Expected Behavior
Nothing
Actual Behavior
Terraform is trying to add a resource that is already created by terraform, after manually adding another firewall rule with different query type for the same domain list. The reason for manually creating the new rule is terraform not yet support query type within
aws_route53_resolver_firewall_rule
. Ref: [Enhancement]: Add support for "Query type" on aws_route53_resolver_firewall_rule #38070Relevant Error/Panic Output Snippet
After terraform apply: (Even though the resource was already created previously by Terraform)
Terraform Configuration Files
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
I have confirmed with AWS that DNS firewall do support multiple rules using the same AWS managed domain list.
References
No response
Would you like to implement a fix?
None