-
Notifications
You must be signed in to change notification settings - Fork 454
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
r/distributed_port_group: Use MOID as resource ID
The additions that are in #201 dictate the basis for how we will be working with vSphere networks in the future - any resource that requires a network for a backing (ie: virtual ethernet cards, VMkernel nics, etc) will require a MOID to some sort of network, versus the name itself, allowing us to circumvent actually searching for the network in the downstream resource itself. Searching would be circumvented altogether in the case of DVS portgroups being managed by TF completely as we would just pass the MOID to the downstream resource. The current behaviour of the vsphere_distributed_port_group resource is to use the key attribute in the MO as the ID of the resource, which is documented in the API as the UUID of the DVS port group, although in reality it actually seems to be the MOID, which allows #201 to work without issue right now. However, in order to guarantee that things will be stable in the long run, we need to be sure we are using the right values, so this update changes the ID to be the MOID of the object itself. key is now being exported as a computed attribute of the same name.
- Loading branch information
1 parent
6f8ba38
commit 71ff4dd
Showing
2 changed files
with
27 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters