d/compute_cluster: New data source #492
Merged
Conversation
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 adds the vsphere_compute_cluster data source, which allows one to look up an existing cluster. It also closes a convenience gap in the provider which has been a point of confusion since around 1.0, in that people looking to supply the resource_pool_id for a virtual machine were confused in that they didn't think they had a resource pool. This now allows someone to specify a cluster directly, and then use the resource_pool_id attribute from this data source as the input to vsphere_virtual_machine.
vancluever
added
enhancement
|
Thanks @bill-rich! |
ghost
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds the
vsphere_compute_clusterdata source, which allows one tolook up an existing cluster.
It also closes a convenience gap in the provider which has been a point
of confusion since around 1.0, in that people looking to supply the
resource_pool_idfor a virtual machine were confused in that they didn'tthink they had a resource pool. This now allows someone to specify a
cluster directly, and then use the
resource_pool_idattribute from thisdata source as the input to
vsphere_virtual_machine.