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

dns_managed_zone datasource fails in 3.0.0-beta1 #4939

Closed
slevenick opened this issue Nov 18, 2019 · 2 comments
Closed

dns_managed_zone datasource fails in 3.0.0-beta1 #4939

slevenick opened this issue Nov 18, 2019 · 2 comments
Assignees
Labels
Milestone

Comments

@slevenick
Copy link
Collaborator

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 "me too" comments, 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
  • If an issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to "hashibot", a community member has claimed the issue already.

Terraform Version

3.0.0-beta1

Affected Resource(s)

google_dns_managed_zone data source

Terraform Configuration Files

data "google_dns_managed_zone" "delegation-zone" {
    name = "zonename"
    project = "my-project"
}

Debug Output

Fails to find due to bad request url

Expected Behavior

Should read dns zone

Actual Behavior

Fails with 404 even if the zone exists

Important Factoids

Due to switching id format in 3.0.0, fix will be available soon via GoogleCloudPlatform/magic-modules#2712

References

  • #0000
@ghost ghost added the bug label Nov 18, 2019
@slevenick slevenick self-assigned this Nov 18, 2019
@slevenick slevenick added this to the 3.0.0 milestone Nov 18, 2019
@slevenick
Copy link
Collaborator Author

This will be fixed in the next release

@ghost
Copy link

ghost commented Dec 19, 2019

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. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Dec 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant