-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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_container_cluster hits 400 when using a network with self_link #5552
Comments
It works if I do this instead:
|
The Google API expects the name of the network, not the resource URL.
|
Some google resources required network be refernced by resource URL (aka self_link), while others required network name. This change allows either to be supplied. DRY it out, and add a fix for hashicorp#5552.
This should now work with either the |
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Trying to apply results in:
The
prod
network exists for sure. When I refresh tf state, it shows up. It also shows up in the list of networks fromgoogle compute networks list
.The text was updated successfully, but these errors were encountered: