Skip to content
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

aws_route53_zone_association_authorization resource got kicked out of aws provider following 3.2.0 (was in 3.1.0) #14825

Closed
bashoKa opened this issue Aug 25, 2020 · 4 comments
Labels
question A question about existing functionality; most questions are re-routed to discuss.hashicorp.com. service/route53 Issues and PRs that pertain to the route53 service.

Comments

@bashoKa
Copy link

bashoKa commented Aug 25, 2020

Hi

The aws_route53_zone_association_authorization resource got kicked out of the 3.2.0 and 3.3.0 releases of the AWS provider. Also it was released in 3.1.0.

Would guess wasn't intended? At least I didn't see something in the release notes?

best / thanks

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • 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
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

`
terraform -v
Terraform v0.12.29

  • provider.aws v3.3.0

    terraform -v
    Terraform v0.12.29
  • provider.aws v3.2.0
    works in:
    terraform -v
    Terraform v0.12.29
  • provider.aws v3.1.0
    `

Affected Resource(s)

  • aws_route53_zone_association_authorization

Terraform Configuration Files

Debug Output

`
terraform validate

Error: Invalid resource type

on main.tf line 99, in resource "aws_route53_zone_association_authorization" "this":
99: resource "aws_route53_zone_association_authorization" "this" {

The provider provider.aws does not support resource type
"aws_route53_zone_association_authorization".

`

Expected Behavior

`
terraform validate
Success! The configuration is valid.

`

Actual Behavior

`
terraform validate

Error: Invalid resource type

on main.tf line 99, in resource "aws_route53_zone_association_authorization" "this":
99: resource "aws_route53_zone_association_authorization" "this" {

The provider provider.aws does not support resource type
"aws_route53_zone_association_authorization".

`

Steps to Reproduce

  1. terraform init
  2. terraform validate

References

@ghost ghost added the service/route53 Issues and PRs that pertain to the route53 service. label Aug 25, 2020
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Aug 25, 2020
@DrFaust92
Copy link
Collaborator

DrFaust92 commented Aug 25, 2020

aws_route53_vpc_association_authorization is the resource that's been added. and resource_aws_route53_zone_association and some changes made to it

@gdavison
Copy link
Contributor

Hi @bashoKa. @DrFaust92's comment above is correct.

@gdavison gdavison added question A question about existing functionality; most questions are re-routed to discuss.hashicorp.com. and removed needs-triage Waiting for first response or review from a maintainer. labels Sep 23, 2020
@pof-ericksonrory
Copy link

Was this an expected removal, are we likely to see this added in a later release?

@ghost
Copy link

ghost commented Oct 24, 2020

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!

@ghost ghost locked as resolved and limited conversation to collaborators Oct 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question A question about existing functionality; most questions are re-routed to discuss.hashicorp.com. service/route53 Issues and PRs that pertain to the route53 service.
Projects
None yet
Development

No branches or pull requests

4 participants