VMware Aria Automation 8.x Deployment References Incorrect Blueprint ID After Source Control Sync

Products

• VCF Automation

Issue/Introduction

When implementing source control or automated content source integrations (such as GitHub) in VMware Aria Automation (vRA) 8.x, duplicate blueprints are created with identical names but distinct unique system IDs. Active deployments remain tied to the legacy blueprint IDs, preventing the deletion of duplicate/manual blueprints without disrupting or destroying existing deployment instances. External backend orchestration services referencing blueprints strictly by name fail due to duplicate naming conflicts.

Environment

 

• VMware Aria Automation 8.x (formerly vRealize Automation)

• VMware Aria Orchestrator 8.x

 

Cause

Importing blueprints via automated content sources generates a new system GUID (blueprint_id) within vRA. Existing active deployments retain foreign key references to the original manual blueprint GUID in the catalog database (catalog-db), creating duplicate entities with identical display names that cannot be cleaned up via standard API/UI procedures while active deployments remain attached

Resolution

Perform a direct database update in the catalog-db PostgreSQL instance on the vRA host to map target deployment IDs directly to the correct source-controlled blueprint_id.

1. Establish an SSH session to the primary vRA appliance as root: ssh root@<vRA_IP>
2. Generate a compressed database dump before performing modifications: vracli db dump catalog-db | xz -c > catalog-db_backup.xz
3. Connect to the catalog-db PostgreSQL instance: vracli dev psql catalog-db
4. Update the target deployment to reference the correct source-controlled blueprint ID: UPDATE dep_deployment SET blueprint_id='<NEW_BP_ID>' WHERE id='<DEPLOYMENT_ID>';