A service blueprint task lets you invoke a plug-in available in the vRealize Automation service catalog from a release pipeline. You can publish a predefined workflow from vRealize Orchestrator to the vRealize Automation service catalog.

The service blueprint task has the following limitations.

When there are multiple tabs in the service blueprint task form only the active tab is validated when you save the task.

String type output parameter values of published catalog items are supported.

String, SecureString, and Boolean string input parameter values are supported in the task execution input parameter text box.

Auto-complete is supported for text boxes that have the gwt-TextBox css property value.

Form field layout and validation logic cannot be overridden.

Plug-ins in the service catalog that are only from local vRealize Automation instances can be invoked.

Verify that a service blueprint is created and published. See the Installation and Configuration guide.

Familiarize yourself with the parameter values that are required to configure and use the vRealize Orchestrator plug-in for Puppet. See the Using the vRealize Orchestrator Puppet Plug-In 1.0 guide.


Click the Code Stream tab.


Select an existing pipeline to configure from the Pipeline tab.


Select Edit > Stages.


Select Add Task.


Select Custom from the Category drop-down menu.

You can also select the Deploy, Provision, or Test categories for the service blueprint task.


Select vRA Service Blueprints from the Provider drop-down menu.


Select a published service blueprint from the drop-down menu.

For example if you are using the published Puppet plug-in workflow, the endpoint would be Add a Puppet Master.


Enter a name for the custom task and click OK.