Deploy-On Mechanism

“Deploy on” mechanism

Depending on the connection type you can deploy the proper blueprint:

The current version of deploy_on_token.yaml/deploy_on_user_password.yaml supports public repo, to use private repo or local blueprint check chapter 7. Resource Config.

Upload the blueprint to SPIRE MANAGER. Filter (refer to chapter 6. Filters, Location and Labels) Environments and click the action “Deploy on” from Bulk action. The dialog appears. Select the proper blueprint and after that the inputs are visible.

Deploy On

Inputs description:

Verification “Deploy on” mechanism

To check if deployments are deployed on local managers, follow the example below/ The examples use uploaded blueprint with id blueprint_on_sub manager. The used inputs to “Deploy on” mechanism:

Go to the Services by clicking on the button.


Verify if the install completed tile is visible in Execution Task Graph.


You can also go to the local manager and check if deployment is installed in the Services tab.

sub manager Deployment

Optional [Only when inputs are exposed in Capabilities] !!! In this blueprint, inputs are exposed. You can check the value of capabilities. Local Capabilities

Filters, Location and Labels


Bulk action “Deploy on” perform actions on all accessible Environments. If you would like to select only a specific sub manager, you can use Filters. You can click the Filter button (next to Bulk actions),and after that, the dialog appears.


Fill it in and click Apply


The site can be set in the Deployment Metadata of Deploy dialog. Set Site

To view the location of the selected Environment, you can click Map button (next to Bulk actions and Filter), and after that the dialog appears.



The user can specify Labels in the Deployment Metadata tile. Labels can be also set via blueprint. Current Labels are present in Deployment Info.


The user can add a label by clicking on Add button.

Resource Config

Node cloudify.nodes.Component allows you to create deployment based on the blueprint which can be uploaded to the target manager (sub manager) from 3 types of resources:

You can also specify inputs of deployments (example here):

    input0: test
    input1: {get_input: value1}
    input2: {get_secret: sec1}

If you use get_secret: secret1, you have to check if secret1 is created.