Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[DOCS] customization_spec is missing from the VMware cloud docs
See original GitHub issueDescription Docs here:
https://docs.saltstack.com/en/master/topics/cloud/vmware.html
talks about enabling customization, but doesn’t document the customization_spec parameter that points to how to customize the instance.
https://github.com/saltstack/salt/blob/master/salt/cloud/clouds/vmware.py#L2805
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Managing the VMware Cloud on AWS Data Center
The Managing the VMware Cloud on AWS Data Center documentation explains how to configure and manage your VMware Cloud on AWS software-defined ...
Read more >VMware Cloud Documentation
VMware Cloud is a modern integrated cloud service for the modern IT environment. Want to know what is new in VMware Cloud? Look...
Read more >VMware PowerCLI Change Log
Change Type, Description. feature. New cmdlets to retrieve, start, stop and restart vSphere appliance services have been added to the VMware.VimAutomation.
Read more >VMware vRealize Automation 8.6.2 Release Notes
Access all your vRealize Automation Cloud documentation in one place ... Azure, AWS networks are marked missing and re-collected as new ...
Read more >Creating and Managing Customization Specifications
VMware Customer Connect Support Policies Product Documentation Compatibility Guide End User Terms & Conditions California Transparency Act ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I ran into the same issue today and was testing customization_spec setting. A positive side effect of being able to select a customization spec, is that the instance will have its hostname set properly, matching the minion id (if your spec is set to use the virtual machine name for Computer name) So no need to run a task (most customers use a state during start up) to set hostname on post deployment.
yeah… I mostly put this issue in to remind myself to eventually get around to it (unless someone steals it from me)