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

provider/vsphere: fix gateway settings in dhcp tests #6635

Merged
merged 1 commit into from
May 12, 2016
Merged

provider/vsphere: fix gateway settings in dhcp tests #6635

merged 1 commit into from
May 12, 2016

Conversation

thetuxkeeper
Copy link
Contributor

Fix for DHCP tests after merging #6522.
cc @chrislovecnm , @jen20

@stack72
Copy link
Contributor

stack72 commented May 12, 2016

LGTM! pending travisci

@thetuxkeeper
Copy link
Contributor Author

thetuxkeeper commented May 12, 2016

@stack72: Wow, that was a fast response :D
Btw. Is it really the right way to set it only as Computed? I mean if you set this setting (not computed) it won't be updated (not implemented). But ForceNew is somehow also wrong since it would redeploy if you change the DHCP gateway not set by terraform.

@stack72
Copy link
Contributor

stack72 commented May 12, 2016

if it can be set by the user and can also be computed then computed and optional is correct

@thetuxkeeper
Copy link
Contributor Author

Ok, thanks. Then we would have to implement the update logic that it works like a user would expect. But that's already on the roadmap.

@stack72
Copy link
Contributor

stack72 commented May 12, 2016

@thetuxkeeper for now, until we get the update logic in place, should these be Optional, Computed (to fix the bug) and ForceNew?

@thetuxkeeper
Copy link
Contributor Author

thetuxkeeper commented May 12, 2016

With ForceNew, would it recreate the VM if you use DHCP (*_gateway not set and computed) and change the gateway with DHCP?
If it's like that we have two choices while the update logic is not there yet:

  1. unnecessary recreation when changing the gateway over DHCP (ForceNew)
  2. or not applying the setting if you set it in the config

But I think an unnecessary recreation is better than not applying changes. But I'm not sure.

If we change it for the gateway settings to ForceNew+Computed, should we change it for the other network settings? The IP address settings should have the same behavior since only Computed is set

@stack72
Copy link
Contributor

stack72 commented May 12, 2016

Got it - let's (IMO) go with the least dangerous one - the not updating (as you have it) and then revisit the update later

@stack72 stack72 merged commit 510b293 into hashicorp:master May 12, 2016
@thetuxkeeper
Copy link
Contributor Author

Ok. Then I know how to set it if something like that appears somewhere else.
Thanks for merging :)

@thetuxkeeper thetuxkeeper deleted the vsphere-fix-gateway-dhcp branch May 12, 2016 12:57
cristicalin pushed a commit to cristicalin/terraform that referenced this pull request May 24, 2016
@ghost
Copy link

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

Successfully merging this pull request may close these issues.

2 participants