Using descriptions AND source control for VCF Automation templates
The source control integration in VCF Automation templates isn't bi-directional and adding descriptions to templates can cause an annoying problem. There is a way around it though.
The source control integration in VCF Automation templates isn't bi-directional and adding descriptions to templates can cause an annoying problem. There is a way around it though.
Using the 'substring' expression in a VCF Automation template caused me a small issue recently. The fix is very simple!
Revisiting the automation of my vSphere Packer builds using GitLab a CI/CD pipeline.