Conductor Documentation

Writing Plugins

Studio Conductor communicates with external services via plugins.

Examples of external services include:

For example, if your blueprint defines an Azure VM, you need the Azure plugin. If your blueprint defines a Kubernetes Deployment, you need the Kubernetes plugin.

Many services can be supported with a generic existing plugin, such as Studio Conductor’s built-in script plugin, for more information, see:

Distribution

Studio Conductor distributes plugins in Wagon format. Wagon packages sets of Python Wheels for dependency management. Studio Conductor publishes official wagons, which are found on plugins download page.

Note: The Script plugin is distributed with cloudify.

Plugin Installation

The first step to using a plugin is to upload the plugin to your Conductor Manager tenant.

To upload a plugin:

Local Python Path Installation

You can also install the wagon in your local Python path:

$ wagon install -s [path-to-wagon-file]

Note: This method is available when working in a Local CLI profile.

Usage

Plugin usage inside of blueprints varies. However, these two general rules apply:

See specific plugin documentation for complete usage information.

Plugin Development

Studio Conductor plugins are Python projects with functions that that may be called by Studio Conductor.

For more information, see creating your own plugin.

For a plugin template, see plugin template.

For information on packaging a plugin in wagon format, see creating wagons.