You can configure the parameter values of the published service blueprints based on Puppet plug-in or other workflows.


  • Verify that a custom service blueprint task is available in a release pipeline.

  • 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.


  1. Open a release pipeline.
  2. Select the new task in the stage.
  3. Confirm to save the pipeline.
  4. Select an Execute Task for the release pipeline.




    Runs the release pipeline task without conditions.

    On Condition(s)

    Runs the release pipeline task only if the defined condition is evaluated as true. If the condition is false, the task is skipped.

    A boolean expression using the following operands and operators is supported.

    • Pipeline variables such as, ${pipeline.variableName}. Curly brackets are reserved for specifying pipeline variables.

    • Task output variables such as, ${Stage1.task1.machines[0].value.hostIp[0]}

    • Default pipeline binding variables such as, ${releasePipelineName}

    • Case insensitive Boolean values such as, true, false, 'true', 'false'

    • Integer or decimal values without quotes

    • String values used with single or double quotes such as, "test", 'test'

    • String and Numeric types of values such as, == Equals and != Not Equals

    • Relational operators such as, > , >=, <, and <=

    • Boolean logic such as, && and ||

    • Arithmetic operators such as, +, -, *, and /

    • Nested expressions using round brackets

    • Strings with literal value ABCD is evaluated as false and the task is skipped.

    Unary operators are not supported.

    A sample condition, ${Stage1.task1.output} == “Passed” || ${pipeline.variableName} == 39

  5. (Optional) Select the Continue Pipeline execution even if this task fails option.

    This option allows the release pipeline to bypass the failed task and continue with the execution process.

  6. Configure the workflow parameters in the release pipeline.

    The parameter values for a plug-in workflow depends on the type of the workflow.

    For example, you can configure the following Puppet plug-in workflows.

    • Add a Puppet Master

    • Validate a Puppet Master

    • Update a Puppet Master

    • Remove a Puppet Master

    • Node Management Workflows

    • Hiera Workflows

    • Manifest Workflows

    • Samples Workflows

    • Experimental Puppet Plug-In Rake Workflows

  7. (Optional) Select the script task output to share the output with other tasks in the release pipeline.

    The output contains the runtime data that is written to the $SCRIPT_RESPONSE_FILE file.

  8. Click Save.

Task Output Format for a Custom Service Blueprint

The following task output format is an example for a custom service blueprint task.

    "description": "master",
    "name": "master",
    "value": "",
    "type": "Puppet:Master"
    "description": "workflowExecutionId",
    "name": "workflowExecutionId",
    "value": "8af0d1274f72d384014fb05beec144a9",
    "type": "STRING"
    "description": "workflowId",
    "name": "workflowId",
    "value": "0ddc5db0-2c43-46af-93cd-b3507fb0fc5b",
    "type": "STRING"
    "description": "__asd_requestedBy",
    "name": "__asd_requestedBy",
    "value": "",
    "type": "STRING"
    "description": "__asd_requestedFor",
    "name": "__asd_requestedFor",
    "value": "",
    "type": "STRING"
    "description": "workflowName",
    "name": "workflowName",
    "value": "Add a Puppet Master",
    "type": "STRING"
    "description": "__asd_tenantRef",
    "name": "__asd_tenantRef",
    "value": "qe",
    "type": "STRING"
    "description": "__asd_subtenantRef",
    "name": "__asd_subtenantRef",
    "value": "4f9adef5-f09e-408b-8427-57cbc18e8e90",
    "type": "STRING"
    "description": "__asd_catalogRequestId",
    "name": "__asd_catalogRequestId",
    "value": "8af0d1274f72d384014fb05bd2bb44a3_96bdad96-91b3-4306-a255-be8049fbe2f2",
    "type": "STRING"