Skip to main content
System StatusContact Support
VersionOne Community

Configuring the Deploy Plugin

This feature is available in Ultimate edition only.

editions-u.png

Overview 

The Automate plugin is maintained by Continuum and is used to launch Automate Tasks. Automate Tasks can be scripted to do just about anything.

Refer to Automate to learn more information on Automate Tasks.

Working with the Deploy Plugin

Creating a Sample Task

The first thing to do is visit the Automate First Task tutorial page. Follow the directions creating a first task and then return here to continue with this tutorial.

Using the Automate plugin

In the Pipeline Editor, edit a stage and from the left side, drag and drop the Continuum Automate "task.runtask" function to the right. At the very minimum, the following json needs to be in the Arguments box.

{
    "task": "taskname"
}

Where taskname is the name of the task that you intend on launching using Automate. For starters use the task name created in the Hello World first task tutorial. This will not pass parameters, we'll explore that next. For now, initiate your sample pipeline, then go to the pipeline instance page for this pipeline. If you click on the stage, then the task you will see the log output from the task run.

Passing Parameters and Other Data

Now let's pass parameters into the task.

{
    "task": "taskname",
    "parameters": [
        {
            "name": "param1",
            "values": [
                "hello"
            ]
        },
        {
            "name": "param2",
            "values": [
                "world"
            ]
        }
    ]
}

The parameters properties will be passed to the task with the name being the parameter name and the values being the parameter values. Notice that the parameters declaration is a list or json array as well as the values declaration. For the parameters declaration obviously a task can support multiple parameters. For the values, each parameter can support multiple values which can be spun through and processed if need be. For instance, a list of ip addresses or a list of tests to perform.

Other supported task.runtask Arguments are included in the following example.

{
    "task": "taskname",
    "version": "1.000"
    "account": "AWS",
    "log_level": "10",
    "parameters": [
        {
            "name": "param1",
            "values": [
                "hello"
            ]
        },
        {
            "name": "param2",
            "values": [
                "world"
            ]
        }
    ]
}

The "version" declaration is the version number of the task to run. "account" would be the cloud account name that the task will run in scope to. This would determine the credentials and possibly cloud name in scope during the task execution. "log_level" is the logging level that the task will run with. 10 = Debug (all available output will be printed to the log), 20 = Info, 30 = Warning, 40 = Error and 50 = Critical (No output to the log except the most critical of runtime errors).

  • Was this article helpful?