[BUG] library.deploy behavior does not match description #2598
Comments
|
Howdy 🖐 nanw1103 ! Thank you for your interest in this project. We value your feedback and will respond soon. If you want to contribute to this project, please make yourself familiar with the |
dougm
added a commit
to dougm/govmomi
that referenced
this issue
Oct 21, 2021
- add example of using library.export to generate options.json Fixes vmware#2599 Fixes vmware#2598
11 tasks
dougm
added a commit
to dougm/govmomi
that referenced
this issue
Oct 21, 2021
- add example of using library.export to generate options.json Fixes vmware#2599 Fixes vmware#2598
yuyin002
pushed a commit
to yuyin002/govmomi
that referenced
this issue
Jan 12, 2022
- add example of using library.export to generate options.json Fixes vmware#2599 Fixes vmware#2598
pradeep288
pushed a commit
to pradeep288/govmomi
that referenced
this issue
Jan 17, 2022
- add example of using library.export to generate options.json Fixes vmware#2599 Fixes vmware#2598
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The library.deploy help text shows something like:
govc library.deploy /library_name/ovf_template vm_name govc library.deploy /library_name/ovf_template -options deploy.jsonThe second example does not match the actual behavior. It always requires a VM name. Deploying using the second example will result a VM named "-options" to be deployed.
Affected version
0.26.1
The text was updated successfully, but these errors were encountered: