Aria Automation Service Broker: Policy Scope Cannot Be Modified After Creation

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Users are unable to change the scope of an existing Service Broker policy in VMware Aria Automation, even when possessing the necessary administrative permissions.

Environment

VMware Aria Automation 8.18 and potentially other 8.x versions.

Cause

This behavior is by design and is documented in the official VMware Aria Automation product documentation. Once a Service Broker policy is created, its defined scope is immutable.

As per the VMware Aria Automation documentation on configuring policy scope:

"The scope options are the same for all policy types. After you create a policy, you cannot change the scope."

Source: Documentation

Resolution

Since the policy scope cannot be modified after creation, the recommended approach is to:

1. Create a New Policy: Create a new Service Broker policy with the desired scope and configuration.

2. Replace and Delete: Once the new policy is active and functioning as intended, delete the old policy that had the incorrect or undesired scope. 

 

Future Enhancement 

A feature request (FR) has been submitted to VMware Engineering to explore the possibility of allowing Service Broker policy scope modification in future releases of Aria Automation.

However, there is no immediate fix or planned release date for this functionality at this time.

Please subscribe to this KB article for any updates regarding this feature request.