Inputs cannot begin with numbers in vRealize Automation Cloud Assembly blueprints
search cancel

Inputs cannot begin with numbers in vRealize Automation Cloud Assembly blueprints

book

Article ID: 314828

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • If an input is created which starts with a number, the input resolution will fail. 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}'

 

  • Here '1stdisk' will not get resolved because we do not support inputs which start with a number.
  • The validation API throws an error similar to:
'Input name must be alphanumeric & cannot start with a number'.


Environment

VMware vRealize Automation 8.3.x

Cause

The parser grammer does not currently support names which start with a number.
 

Resolution

This is by design and consumers should leverage a Java like naming convention and avoid naming inputs beginning with numbers.

Additional Information

Impact/Risks:

This applies to both blueprint inputs & property group inputs.