Hi All,
We're trying to hide the above fields for our deployment, relying on a drop-down box for CPU/Memory/Disk configuration through setting custom properties. Unfortunately, the inputs for #CPUs, MemoryMB and StorageGB are still visible to the end-user doing the provisioning. This is undesirable, as we want them to select from pre-defined, discrete values.
For example, when I select "Small", I get a VM with 1 vCPU and 2GB RAM. When I select "Medium", I get a VM with 2vCPUs and 4GB RAM. The configuration of these properties is currently done in vCO; all I want to do is hide the inputs for CPU/ Memory/ Disk so that the user doing the provisioning is not confused.
To elaborate:
Additionally, I've configured the property dictionary to give some context around this sizing dropdown, through the use of a property dictionary with a 'notes' and 'label' property. These don't display on the blueprint when deploying! Is this a bug? See the following for what I mean:
The documentation seems to indicate that I can use these to wrap some context around the deployments (eg. add notes and labels). Can somebody please elaborate as to how these are used?
Thanks,