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 Compute's google_compute_instance_template.network_interface.network should be a URL #3226

Closed
sorccu opened this issue Sep 12, 2015 · 5 comments

Comments

@sorccu
Copy link

sorccu commented Sep 12, 2015

On Terraform v0.6.3, it looks like google_compute_instance_template.network_interface.network is not supposed to be a network name like the documentation suggests. You will get the following error:

* google_compute_instance_template.foo: Error creating instance: googleapi: Error 400: Invalid value for field 'resource.properties.networkInterfaces[0].network': 'bar'.  The URL is malformed., invalid

Using the network's .self_link works.

The "Example Usage" on that page should also be wrong, unless there is some sort of special handling for the "default" network.

@lwander
Copy link
Contributor

lwander commented Sep 15, 2015

Oddly enough, "default" works on its own. I think it would be neater to simply provide a network name rather than note in the documentation to provide a URI to the network. What do you think?

@sorccu
Copy link
Author

sorccu commented Sep 15, 2015

I think it would be best to go for consistency, so that "default" isn't a special case. I'd prefer just using the network name.

@lwander
Copy link
Contributor

lwander commented Sep 15, 2015

Sounds good, I'll make the fix

@lwander
Copy link
Contributor

lwander commented Oct 6, 2015

@sorccu, @sparkprime : fixed by #3242

@ghost
Copy link

ghost commented Apr 30, 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 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.

@ghost ghost locked and limited conversation to collaborators Apr 30, 2020
This issue was closed.
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

4 participants