Working with Blueprints

After creating Stack Providers and Stack Templates, as an Administrator, you create Blueprints that contain the required infrastructure to set up a new Environment.

Important! The actions that you can perform depend on your folder permissions. See: Assigning Release Automation Permissions.

This page includes the following:

About Blueprints

A Blueprint is the prescription for the creation of a CDA Environment (which, in turn, contains multiple CDA Deployment Targets). A Blueprint consists of a Stack Template and the corresponding Deployment Target types needed to provision the Environment.

Note: A Blueprint can consist of multiple Stack Templates.

Viewing Blueprints

  1. Go to the Release Automation perspective.
  2. Click the Provisioning accordion tab.
  3. Select Blueprints.

Note: To see the list of Blueprints where a certain Stack Template is used, open the Stack Template and select the Blueprints tab.

Tip: For more information about how search for entities and narrow down the results, see Advanced Search.

Creating Blueprints

  1. Go to the Release Automation perspective.
  2. Click the Provisioning accordion tab.
  3. Select Blueprints.
  4. Click the Create button in the toolbar. The Create Blueprint dialog is displayed.
  5. Enter a name for the Blueprint.
  6. From the Folder drop-down list, select a folder to store the new Blueprint. If no folder is selected, the Blueprint is stored in the default location.
  7. Define an owner for the provider. The current user is selected by default.
  8. Click Create.
  9. The properties Properties view is shown. You can optionally add a description to better identify the Blueprint at a later point in time.

  10. If you want to assign a Stack Template to the Blueprint, click the Stack Templates tab and select one or more Stack Templates from the list.

What to do next:

Changing Properties of Blueprints

Properties can be changed:

You can change the following properties:

Exporting Blueprints

  1. Go to the Release Automation perspective.
  2. Click the Provisioning accordion tab.
  3. Select Blueprints.
  4. Open the Blueprint you want to export.
  5. Expand the Export accordion tab and click JSON. The Blueprint and the Stack Templates assigned (if any) are displayed in JSON format.

Note: You can copy the text to the clipboard to create another similar Blueprint via the REST API.

Duplicating Blueprints

  1. Go to the Release Automation perspective.
  2. Click the Provisioning accordion tab.
  3. Select a Blueprint from the list.
  4. Click the Duplicate icon in the toolbar. The Duplicate Blueprint dialog is displayed.
  5. Enter a name for the duplicated Blueprint.
  6. Select a folder to store it.
  7. Click Create.

Provisioning Blueprints

There are two starting points to provision Blueprints:

This section describes how to provision Blueprints from the Blueprints list.

Note: Archived Blueprints cannot be provisioned.

To Provision Blueprints

  1. Go to the Release Automation perspective.
  2. Click the Provisioning accordion tab.
  3. Select Blueprints.
  4. Click the Provision button in the toolbar. The Provision Environment from Blueprint dialog is displayed.
  5. Enter a name for the new Environment.
  6. From the Folder drop-down list, select the folder where you want to store your Environment.
  7. Define an owner. The current user is selected by default.
  8. Click Provision.

Now the deployment Workflow can be executed.

Deleting Blueprints

Note: You may only delete the entity when you have the appropriate permission on the containing folder (see Security Concept in CDA) and all of the listed conditions are met.

Conditions to delete entities of type Blueprints: