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

Allow Users to Choose Content Library for OVF Deployments #514

Closed
dfoley84-zz opened this issue Nov 20, 2020 · 3 comments · Fixed by #515
Closed

Allow Users to Choose Content Library for OVF Deployments #514

dfoley84-zz opened this issue Nov 20, 2020 · 3 comments · Fixed by #515
Assignees
Labels
feature_request New feature or request has_pr
Milestone

Comments

@dfoley84-zz
Copy link

dfoley84-zz commented Nov 20, 2020

SUMMARY

Unlike the Module "community.vmware.vmware_content_deploy_template" Where you have the ability to pick which Subscription you wish to deploy from. The module Deploying OVF from Content Library doesn't have this feature, which it appears to pick at random a subscription to deploy from. In doing so, to double the time needed for a deployment workflow.

ISSUE TYPE
  • Add the Feature content_library
COMPONENT NAME

community.vmware.vmware_content_deploy_ovf_template

ADDITIONAL INFORMATION
---
    - name:
      hosts: localhost
      gather_facts: false
      connection: local
      tasks:
      - community.vmware.vmware_content_deploy_ovf_template:
          host: "{{ esxi_hostname }}"
          hostname: "{{ vcenter_hostname }}"
          username: "{{ user }}"
          password: "{{ pass }}"
          datacenter: "{{ datacenter }}"
          cluster: "{{ cluster }}"
           content_library: "{{ library_name }}" 
          datastore: "{{ datastore }}"
          resource_pool: "{{ vmname }}-resource"
          validate_certs: False
          folder: vm
          ovf_template: "{{ TemplateName }}"
          name: "{{ vmname }}"
        delegate_to: localhost
@mariolenz
Copy link
Collaborator

@dfoley84

Can you please have a look at #515 and tell us if it works for you?

@Akasurde
Copy link
Member

resolved_by_pr #515

@Akasurde Akasurde added the feature_request New feature or request label Nov 21, 2020
@Akasurde Akasurde added this to the v.1.5.0 milestone Nov 21, 2020
@dfoley84-zz
Copy link
Author

Thanks for the Quick Turn around on the Feature Request, I see that #515 is in progress, will close this Issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature_request New feature or request has_pr
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants