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_route next_hop_network is not an input (doc error) #5556

Closed
leighmhart opened this issue Mar 10, 2016 · 6 comments
Closed

google_compute_route next_hop_network is not an input (doc error) #5556

leighmhart opened this issue Mar 10, 2016 · 6 comments

Comments

@leighmhart
Copy link

https://www.terraform.io/docs/providers/google/r/compute_route.html

lists next_hop_network as an optional input. According to https://cloud.google.com/compute/docs/reference/latest/routes this is an output only.

Regards,

@phinze
Copy link
Contributor

phinze commented Mar 10, 2016

Hi @allandrick - thanks for the report.

I just checked, and it looks like we pass NextHopNetwork into the Route create API call. So perhaps the doc bug is on the upstream side?

NextHopNetwork: nextHopNetwork,

Let's check w/ @lwander here.

@lwander
Copy link
Contributor

lwander commented Mar 10, 2016

Looks like that attribute has been set like that since it was first added: https://github.com/hashicorp/terraform/blame/master/builtin/providers/google/resource_compute_route.go#L61. I don't think it's a docs error on the Google side, since it's possible to set attributes in the object sent the API that are simply ignored. @phinze, if we add computed: true to next_hop_network, and leave optional: true, will it break anyone's .tf file that has been supplying next_hop_network? Even though that field has likely been ignored by the API so far.

@phinze
Copy link
Contributor

phinze commented Mar 10, 2016

@lwander if the field has been ignored up until now, I think it's probably fine to just switch it straight to read only - since that should present a straightforward plan-time error. We can add a note to the top of the changelog to explain. What do you think?

@lwander
Copy link
Contributor

lwander commented Mar 10, 2016

SGTM!

@lwander
Copy link
Contributor

lwander commented Mar 10, 2016

PR fixing this was merged.

@lwander lwander closed this as completed Mar 10, 2016
@ghost
Copy link

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