Skip to content
This repository has been archived by the owner on Jan 6, 2023. It is now read-only.

Add support for vagrant-vsphere memory and cpu #163

Merged
merged 1 commit into from
Jan 26, 2022
Merged

Add support for vagrant-vsphere memory and cpu #163

merged 1 commit into from
Jan 26, 2022

Conversation

mannahusum
Copy link
Contributor

vagrant-vsphere uses its own way of configuring memory and number of cpus. This needs to be reflected in the template for the Vagrantfile

@ssbarnea ssbarnea changed the title Add support for github.com/nsidc/vagrant-vsphere Add support for vagrant-vsphere memory and cpu Jan 26, 2022
@ssbarnea ssbarnea added the enhancement New feature or request label Jan 26, 2022
@ssbarnea ssbarnea enabled auto-merge (squash) January 26, 2022 08:43
Copy link
Member

@apatard apatard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Too bad that they can't use all the same names. I gues that we'll have to live with that.

@ssbarnea ssbarnea merged commit d07e1eb into ansible-community:main Jan 26, 2022
@mannahusum
Copy link
Contributor Author

Thank you for merging my pull request so quickly 😃

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

Successfully merging this pull request may close these issues.

3 participants