vRA blueprint fails validation with "resource dependsOn contains invalid resource names" when using conditional logic

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

In Aria Automation blueprints, attempting to use an input variable or conditional logic within the dependsOn: stanza to dynamically determine resource dependencies results in a blueprint validation error.

The goal is to conditionally include a dependency (e.g., vm_2 depends on vm_1) only when a specific input condition is met (e.g., both VMs have SAN disks).

Symptom: The blueprint editor/designer displays the following validation error: resource dependsOn contains invalid resource names

 

Environment

Aria Automation 8.x

Cause

This behavior is expected. The dependsOn: property is a deployment flag used to establish the correct dependency graph before the deployment engine begins execution.

During the blueprint validation phase, vRA requires the values within dependsOn: to explicitly and statically list valid resource names defined within the blueprint. The platform does not fully process complex runtime conditional logic (like a ternary operator evaluating an input value) at the blueprint validation stage to determine the dependency list. When the conditional logic is used, the validator sees a non-static, non-resource list value, leading to the "invalid resource names" error.

Resolution

The most direct workaround for controlling resource build order is to use two separate blueprints or deployments and manage the dependency externally.