When you create a blueprint in vRealize Automation Cloud Assembly, the design canvas includes resource types for the supported cloud account and integration endpoints. You might have use cases where you want to create blueprints based on an expanded list of resource type. You can create custom resources, add them to the design canvas, and create blueprints that support your design and deployment needs.

Use vRealize Orchestrator to create custom resources

Each custom resource is based on a vRealize Orchestrator workflow. You can use the workflows that already exist in vRealize Orchestrator, or you can create your own. Using vRealize Orchestrator to create anything-as-a-service/XaaS workflows means that you can create a blueprint that adds an Active Directory user to machines at deployment time, or add a custom F5 load balancer to a deployment.

In addition to the examples provided here, other examples are provided on blogs.vmware.com.

This example shows you how to create a virtual machine folder.

External type constraints

External types define the type of custom resource in vRealize Orchestrator. For example, VC:VirtualMachine or AD:UserGroup.

When you define your custom resources, you can use the same external type once per shared custom resource, and also once per project. For example, you can create a Simple VM custom resource based on VC:VirtualMachine for a custom resource that is available to any project, for Project A, and for Project B. You cannot create a Linked Clone VM custom resource based in VC:VirtualMachine for all project, Project A, or Project B. You could create a Linked Clone VM custom resource for Project C.