Custom resource update doesn't work after template change in Aria Automation

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• A new field or value has been added to a template in automation.
• Updating the value works for newly created deployments but not for older deployments.
• It is impossible to update the new field for older resources using the custom form.

Environment

Aria Automation 8.18.1 cumulative patch 4

Cause

The affected deployments are still on an older version of the template without the new custom field. 

Resolution

1. Update the deployments to the latest version of the template which has the new resource value/field. 
2. Re-attempt the update of the custom value/field.

Additional Information

While it is possible to update each deployment individually, this could be automated via the following methods:

 1. vRO (vRealize Orchestrator) workflow —

Write a workflow that does the following: 
- Queries all deployments from the old blueprint version via the catalog API
- Iterates over each one and fires POST /blueprint/api/blueprint-requests with the new blueprintVersion and deploymentId
       

This is the most native approach if using embedded vRO

   
2. ABX Action (JavaScript/Python) — Similar loop but as a serverless action

3. Script using the REST API directly — A simple shell/Python script hitting POST /blueprint/api/blueprint-requests in a loop