Input resolution fails for Inputs in a blueprint that start with a number

Products

• VMware Aria Suite

Issue/Introduction

Beginning with VMware Aria Automation 8.6 (formerly VMware vRealize Automation), blueprints with inputs that start with a number will fail during input resolution.

Example:

formatVersion: 1
inputs:
  bootdisk:
    type: string
    default: 'diskmode:independentPersistent'
  1stdisk:
    type: string
    default: 'diskmode:Dependent'
resources:
  Cloud_vSphere_Disk_1:
    type: Cloud.vSphere.Disk
    properties:
      capacityGb: 1
      constraints:
        - tag: '${input.1stdisk}'
  Cloud_vSphere_Machine_1:
    type: Cloud.vSphere.Machine
    properties:
      imageRef: win2019-sql17
      cpuCount: 1
      totalMemoryMB: 1024
      attachedDisks:
        - source: '${resource.Cloud_vSphere_Disk_1.id}'
      storage:
        constraints:
          - tag: '${input.bootdisk}

In the above example, 1stdisk will fail to resolve.

Environment

VMware vRealize Automation 8.x
VMware Aria Automation 8.x

Resolution

VMware Aria Automation 8.6 and above parser grammar does not support names which start with a number.

This is by design.

Blueprint developers and creators should use Java-like naming conventions.