You can use the REST API content management service to import and export content, such as blueprints, between vRealize Automation systems.
About this task
vRealize Automation customers often experiment with system artifacts such as catalog items, XaaS services, resource actions, and IaaS blueprints in their development or staging environments. When appropriate, users need to move these artifacts to their production environments.
You cannot import/export approval policies or entitlements. Also, you cannot import or export any content that is in a draft state.
The examples herein are shown as Curl commands for consistency with other similar examples, though the REST API content management service provides a convenient mechanism for moving such artifacts between systems using the CloudClient interface. With CloudClient, there is no need to set heading values, including the Authorization header. The $host//$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.
Some parameters on the API request are common to all content management service import and export commands. These parameters are listed below.
Parameter |
Description |
---|---|
$host |
The host name and fully qualified domain name or IP address of the vRealize Automation identity server. |
$token |
A valid HTTP bearer token that includes necessary credentials. |
When exporting content, values of secure strings and encrypted properties are excluded by default. You can add the --secure false parameter to commands to export these properties as plain text with your content. Secure strings and encrypted properties are typically used as property holders for passwords.
The following examples illustrate the types of requests that you might use in typical import export situations.
Prerequisites
Log in to vRealize Automation with an appropriate role. For example: Software Architect, Application Architect, Infrastructure Architecture or some combination of these depending on the need.
Verify that the host name and fully qualified domain name of the vRealize Automation instance are available.
Verify that there is a valid HTTP bearer token that matches your login credentials. See REST API Authentication.