Dell Automation Platform: Blueprint inputs cannot be changed

When deploying a new blueprint, or adjusting an existing blueprint; the ability to change inputs is not an option under input override. This maybe inputs such as vCPUs or System Memory of the VM. 

WARNING: Editing ISV blueprints may cause unintended issues – see blueprint guides on infohub.

NOTE: making inputs visible and updatable may not always work as expected, proceed with caution.

• EXAMPLE: Changing a VM to boot in UEFI, when it was configured as BIOS, may prevent the VM from booting.

Custom blueprints allow for the control of configurable inputs during a deployment. The blueprint file, inputs_common.yaml, controls VM inputs. File location varies between different blueprints.

The example of a blueprint below confirms:

• vcpus assigns 4, and is hidden 
• memory_size assigns 4GB and is hidden

NOTE: if allow_update is set to false, there may be other factors in setting this attribute. Consult with the blueprint creator before making these changes.

vcpus:
  type: integer
  hidden: true
  allow_update: true
  display_label: vCPUs
  default: 4

memory_size:
  type: string
  hidden: true
  allow_update: true
  display_label: Memory Size
  description: |
    Memory size with unit [KB,MB,GB,TB,PB,EB,ZB,YB].
    See more about sizing recommendations:
    https://docs.litmus.io/litmusedge/quickstart-guide/system-requirements
  default: 4GB

An blueprint creator may initially decide to obfuscate certain configurable inputs. If there is a requirement to change this later, the blueprint may be adjusted and updated. In the example below, the focus is on a custom blueprint, demo-test-rt, which was initially configured with vCPUS and memory hidden.

To expose inputs that are hidden:

1. From the Orchestrator UI go to Inventory > Blueprints > locate the blueprint and tick the box.
2. From the More dropdown, select Download to Local to download the blueprint as a Zip to locally.
3. Locate the Zip locally, and extract the blueprint.
4. Locate the file inputs_common.yaml. 
5. Update hidden: True to hidden: False on the inputs required. Save and close any files within the blueprint directory.
6. Zip the entire directory, along with the altered files, ensuring the blueprint files are present on the first level of the Zip.
7. Navigate back to the Orchestrator UI, ensure that the blueprint is still selected, and select Update, from the More dropdown.
8. Select a newer Revision, and browse the local machine to upload the updated blueprint Zip. Click Update to push the blueprint to Orchestrator.

When attempting to update a current deployment, or create a new deployment, from Blueprint Revision select the newer version. Under Input overrides vCPUs, and Memory Size should be available for adjustment.

NOTE: adjusting inputs such as Memory Size, or vCPUs, requires a VM reboot. This is done as part of the blueprint update, and should be planned accordingly.