Update CloudConfig Data via Extensibility in Aria Automation
Article ID: 411950
Updated On:
Products
Issue/Introduction
Use case: Update/Create cloudconfig data as part of extensibility during a deployment.
Reasons to perform CloudConfig update via Extensibility:
- Deployment logic - CloudConfig variables or content needs to be updated based on certain deployment logic.
Example cloudconfig logic changes based on external integration after deployment submission.
- Simplify the Cloud Template or facilitate easier updates of cloudconfig - In some cases, the cloudConfig data can be very complex, which can complicate the Cloud Template configuration and YAML formatting requirements.
Moving the cloudConfig to a code update by extensibility simplifies the Cloud Template configuration.
Environment
Aria Automation 8.18.x
Resolution
Extensibility States to use for Update:
Any extensibility state can be used as long as it exists before the system resource is created, and the event state supports the update of the customProperties.
An example is the Compute Allocation event state [compute.allocation.pre]. The Extensibility state being used must additionally support Blocking, as the Workflow/ABX action must update the properties payload with the new cloudconfig data.
Custom Properties for update:
customProperties.cloudConfig - This property exists but currently cannot be updated via extensibility.
customProperties.__computeConfigContent - This is a hidden custom property that allows for update during deployment. Note: This property is not intended for external update and is not officially supported.
Extensibility Workflow Requirements:
- inputProperties - Aria Automation payload Extensibility Input of type “Properties”. Must be “Input” of the workflow.
- customProperties - Aria Automation payload Extensibility Output of type “Properties”. Must be “Input” of the workflow.
Workflow Scriptable Task example of cloudConfig data update and setting property for output and payload update:
Feedback
