Custom properties update on a PKS Cluster deployment which includes custom resources
search cancel

Custom properties update on a PKS Cluster deployment which includes custom resources

book

Article ID: 417332

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When updating custom properties on a PKS Cluster deployment which includes Custom.####_#### and Custom.##_#### resources it fails. Attempts to update the properties through the IaaS API or Deployment API do not reflect the changes in the deployment. Even though the API call returns successfully, the modified properties do not appear in the deployment’s resource properties, and the deployment still reflects the old values.

Environment

VMware Aria Automation 8.18.1

Cause

Properties of a custom resource are managed through VMware Aria Orchestrator (vRO), which is responsible for handling the full lifecycle of these resource types. When a deployment includes custom resources (such as Custom.####_#### and Custom.##_#### objects), their properties are not directly updated through the IaaS or Deployment API. Instead, these APIs rely on the lifecycle workflows defined in Orchestrator.

Resolution

Workaround:

To enable updating of custom properties for custom resources:

Develop and map an Update workflow in VMware Aria Orchestrator for the specific custom resource.

For a custom resource to support updates, there must be a dedicated Update workflow associated with the custom resource type.