The following template structure can be referenced when writing a blueprint.
tosca_definitions_version: cloudify_dsl_1_3
description: >
Input and outputs - describing the most basic blueprint structure
imports:
- https://cloudify.co/spec/cloudify/6.3.0/types.yaml
inputs:
hello:
description: Say Hello to
default: World
node_templates:
MyResource:
type: cloudify.nodes.ApplicationModule
capabilities:
hello:
value: { get_input: hello }
When creating a blueprint, you must update the description, imports, inputs, and capabilities sections. The following explains the information that is required in each section:
- The description section is a free-text field to describe the purpose and usage of the blueprint.
- The imports section is where you add relevant resource provider libraries such as plug-ins that are used in the blueprint.
- The inputs section defines the arguments that you can pass and that are required to run the blueprint. An input can have a default value which is used when no value is provided. An input can also be constrained to ensure that the value provided is valid and is shown as a drop-down list in the web user interface.
- The capabilities section exposes the relevant resources to the outside world. A capability is often an API endpoint, website URL, or other information that is required to access the environment. Capabilities are used by end users such as the user who deployed the blueprint. They are also used by other blueprint deployments.
You can also include additional syntax in the blueprint to add further functionality. For more information about the additional syntax that you can add to a blueprint, see Develop a blueprint.
The blueprint is then automatically validated when uploaded into the Dell Telecom Infrastructure Automation Suite.