-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
resource/aws_route53_record: Remove deprecation from allow_overwrite
argument
#8274
Conversation
…` argument Reference: #7846 Route53 Record `UPSERT` on creation does have some minor valid use cases. We will keep this argument for now while discouraging its usage in the documentation. Output from acceptance testing: ``` --- PASS: TestAccAWSRoute53Record_allowOverwrite (149.81s) ```
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Optional: true, | ||
Computed: true, | ||
Deprecated: "The next major version of the Terraform AWS Provider will require importing existing records", | ||
Type: schema.TypeBool, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where there any tests removed when the attribute was deprecated that should be restored?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope we don't tend to remove testing on deprecations as the functionality is still expected to work as it did previously. 👍 Here's the deprecation pull request for verification: #7734
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Closes #7846
Route53 Record
UPSERT
on creation does have some minor valid use cases. We will keep this argument for now while discouraging its usage in the documentation.Output from acceptance testing: