Allow template names to include a VM folder path #48
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.
Description
VMs or templates to be cloned can now be inside of folders or subfolders.
Issues Resolved
Until now, templates or VMs to be cloned had to be placed in the vSphere's datacenter root directly. For better organization, most setups use folders to group templates - often being nested several levels deep.
Due to the find_vm method being non-recursive, using anything within folders was not possible before (#29). By converting the lookup to use the inventory path instead (format: "DATACENTER/vm/FOLDER/VM"), this now provides the ability to use both templates within the datacenter root (just as before) as well as within subfolders.
Check List