A release pipeline can configure a task to run a workflow that you create in the vRealize Orchestrator service. The task can use either an embedded or an external instance of the vRealize Orchestrator service.
You can use the embedded instance of the vRealize Orchestrator service, which is the instance that is already running on the same appliance. When you use the embedded instance, an endpoint is not needed.
You can also use an external instance of vRealize Orchestrator. When you use an external instance, you must define an endpoint. You must also tag the workflow, and use the correct data types.
Whether you use an embedded or external instance of the vRealize Orchestrator service, you must register the workflow, and use the correct data types.
To register the vRealize Orchestrator service with vRealize Code Stream, you must tag the workflow with the keyword named vRCS_CUSTOM. Untagged workflows do not appear in vRealize Code Stream.
Use only the string data type for the input and output properties. vRealize Code Stream cannot run workflows that use complex data types, or any other data type.
Verify that a workflow is created in vRealize Orchestrator.
- Log in to the vRealize Orchestrator client to create a workflow.
The Tag workflow is required for workflows. By default, the Manual Task workflow is provided.
- Right-click Tag workflow and select Start Workflow.
- To select the workflow, click the Tagged Workflow text box.
For example, the tagged workflow can be Deploy Spring Travel.
- For the tag, enter vRCS_CUSTOM.
- For the value, enter vRCS_CUSTOM.
- For the Global tag, click Yes, and click Submit.
- In vRealize Automation, click the Code Stream tab to continue with the task configuration.