XaaS Limitations

VMware Aria Automation 8 includes these XaaS Limitations.

If your source environment contains multiple Xaas Blueprints or Custom Resources, they are assessed and migrated these ways:

• If the XaaS Blueprints or Custom Resources belong to the same business group, they are detected during the migration assessment but are blocked for migration. You must unpublish all XaaS Blueprints or Custom Resources except for one. The remaining published XaaS Blueprint or Custom Resource can be migrated. You can then publish the remaining XaaS Blueprints or Custom Resources and remigrate. Remigration only migrates the new content while preserving the previously migrated content.
• You can't have two XaaS blueprints configured to the same workflow. When you have 2 or more XaaS Blueprints or Custom Resources that belong to different business groups but are configured to the same workflow, they are not detected during the migration assessment. When migrated, the first migrated XaaS Blueprint or Custom Resource creates the VMware Aria Automation 8 XaaS Cloud Template or Custom Resource and is linked to the workflow. As a result, the subsequent XaaS Blueprints or Custom Resources are not configured to the workflow during migration.
• If multiple XaaS Blueprints contain the same custom resource but use different create, update, and delete workfows, the migrated custom resource only uses the workflows associated with the first migrated XaaS Blueprint. When migrated, all other XaaS Blueprints containing the same custom resource issue an error regarding missing input/output parameters for the custom resource.