-
Notifications
You must be signed in to change notification settings - Fork 9.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Error: PublicZoneVPCAssociation: Attempting to associate public zone #32773
Labels
bug
Addresses a defect in current functionality.
service/route53
Issues and PRs that pertain to the route53 service.
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
github-actions
bot
added
service/route53
Issues and PRs that pertain to the route53 service.
needs-triage
Waiting for first response or review from a maintainer.
labels
Jul 31, 2023
EugenKon
changed the title
[Bug]:
[Bug]: Error: PublicZoneVPCAssociation: Attempting to associate public zone
Jul 31, 2023
justinretzolk
removed
the
needs-triage
Waiting for first response or review from a maintainer.
label
Jul 31, 2023
The plan:
|
As workaround I manually removed managed by terraform DNS records except NS and SOA |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Addresses a defect in current functionality.
service/route53
Issues and PRs that pertain to the route53 service.
Terraform Core Version
1.5.4
AWS Provider Version
5.10.0
Affected Resource(s)
aws_route53_zone
Expected Behavior
No error
Actual Behavior
Same as here #251
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
I do not have exact steps. What I did:
var.use_dns
was assigned tofalse
socount
is changed from 1 to 0.Debug 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: