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

google_dns_managed_zone reference network by id doesn't work #6972

Closed
MBarendregt opened this issue Aug 7, 2020 · 6 comments
Closed

google_dns_managed_zone reference network by id doesn't work #6972

MBarendregt opened this issue Aug 7, 2020 · 6 comments

Comments

@MBarendregt
Copy link

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 the 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 the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

Documentation mentions that in the configuration for google_dns_managed_zone, a network can be referenced the following way:

  private_visibility_config {
    networks {
      network_url = google_compute_network.network-1.id
    }
}

However, referencing it by its id results in:

Error creating ManagedZone: googleapi: Error 400: Invalid value for 'entity.managedZone.privateVisibilityConfig.networks[0].networkUrl': 'projects/someprojectname/global/networks/some-vpcname', invalid

New or Affected Resource(s)

*google_dns_managed_zone

Potential Terraform Configuration

Referencing self_link does work

  private_visibility_config {
    networks {
      network_url = google_compute_network.network-1.self_link
    }
}
@edwardmedia
Copy link
Contributor

edwardmedia commented Aug 10, 2020

@MBarendregt what provider version are you using?

@MBarendregt
Copy link
Author

@edwardmedia, i have to admit, didn't go through to process of trying the beta provider.

But I'm using the normal google provider
tf version, 0.12.25
google version, 3.20

@ghost ghost removed the waiting-response label Aug 15, 2020
@edwardmedia
Copy link
Contributor

@MBarendregt there was a feature that was released with v3.26.0. Can you try with provider's latest version, and let me know how it works? Thanks

https://github.com/hashicorp/terraform-provider-google/blob/master/CHANGELOG.md#3260-june-15-2020

@edwardmedia
Copy link
Contributor

@MBarendregt do you still see the issue with the latest version of the provider?

@edwardmedia
Copy link
Contributor

@MBarendregt Closing this issue assume you no longer see the problem. Feel free to reopen it if you see it again. Thanks

@ghost
Copy link

ghost commented Sep 22, 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. 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 Sep 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants