So I was hoping someone had some input on this issue.
I had property group of CN where it was set to 3 strings of
Previously I set the template YAML to:
formatVersion: 1
inputs:
CN:
type: "object"
title: "Custom Naming"
$ref: "/ref/property-groups/ISPOCN"
- resources:
- Cloud_vSphere_Machine_1:
- type: Cloud.vSphere.Machine
Where name was the shortened letter designation for what OS the template was [W or L]
And then the Custom Naming Template for machine was set to
${project.name}${resource.name}${input.CN.APP}${input.CN.B_FUNC}${input.CN.C_ENVT}${##}
For some reason, only the updated input taken was the input.CN.APP. The other two, regardless of what I updated them to, was stuck at the default.
To fix this, I modified
formatVersion: 1
inputs:
CN:
type: "object"
title: "Custom Naming"
$ref: "/ref/property-groups/ISPOCN"
- resources:
- Cloud_vSphere_Machine_1:
- type: Cloud.vSphere.Machine
- properties:
- shortOS: W
- name: ${self.shortOS + input.CN.APP + input.CN.B_FUNC + input.CN.C_ENVT}
And set the Custom Naming template for Machine to
${project.name}${resource.name}${##}
This has since fixed the updated input values for all 3 custom property groups from not getting added to the custom name.
But now the last issue, where APP is just a string, the B_FUNC is a list of enumerated pairs. In vRA 7, we were able to update the string to something beyond the enumerated values if desired. But in vRA 8 / Aria Automation 8, we are stuck with the enumerated values for the Function designation. Thoughts?
Damion Terrell . + (He/Him) + . * . + @ + . * . + .
Core IT Service Specialist * . + * . + . + . + * +
UNM – IT Platforms – VIS + . . . . . . . . .
. + . + * . + * .
* . . + . . . . + . + * + .
“You learn the job of the person above you, * + . + * @
and you teach your job to the person below you..” . * +
