Blueprints are chaining of multiple templates in the desired sequence, creating very complex automation workflows. Specific templates within the sequence can be scheduled for recurring executions such as daily back-ups.
A pop-up as shown below is displayed, that captures the required inputs to create the Blueprint. Typical metadata required for the Blueprint are Name, Description, Scope – very similar to that of Template/Script/Policies.
Beyond that the input required is the list of templates to be executed in the preferred sequence. This can be done by selecting the templates from the left-side box to the one on right side.
The configuration of a blueprint has the following elements:
- Specify a meaningful name to each of the templates selected. While these are templates, provide a name that implies the sub-action within the blueprint that it achieves.
- Specify the execution type for each template – whether On-Demand (Triggered manually) or Scheduled. If Scheduled is selected, you can later specify the frequency of execution.
- The next step would be to configure the relationship between the selected templates. To define the relationship between templates, you can map the output parameter(s) published by one template as the input parameter for a subsequent template. This will automatically set the dependency/relationship between templates and reduce the number to manual input parameters required during execution.
Once created, the blueprint will be listed in a table as below and can be executed any time.
The execution of a Blueprint is very similar to executing a template. However, Blueprint is an aggregation of multiple templates and hence the values required for all the embedded templates are to be provided for executing the blueprint. However, the input parameters for which the output of previous templates are mapped, will NOT require user inputs while execution.