Importing and Exporting Content

You use the content management service to import and export content such as blueprints, software components, and other artifacts between vRealize Automation systems.

vRealize Automation customers often experiment with system artifacts in their development or staging deployments. When ready, they can use the content management service to move the artifacts to production environments or between different tenants.

Import and export has some known constraints.

Table 1. Import and Export Considerations

Issue	Consideration
Approval policies and entitlements	You cannot import or export approval policies or entitlements.
Required secure property values	If you export a blueprint that has the option --secure true, the values are removed during the export process. If the secure property is marked required, the import process will fail unless you update the package with the secure property values before you import it.
Draft state	You cannot import or export any content that is in a draft state.

For consistency with other service examples, each example lists a curl command. However the content management service provides a convenient mechanism for moving artifacts between systems using the CloudClient interface. With CloudClient, there is no need to set heading values, including the Authorization header. The $vRA//$servicename/api is eliminated from the URL and the service name becomes a separate parameter. For example, consumer/entitled CatalogItems/{id}/request/template. See Using vRealize CloudClient.

XaaS services are integrated with the content management service, and all commands that work with other content types also work with XaaS content to migrate XaaS content into vRealize Automation.

The same set prerequisites apply to each example.