Selecting Primary Command

Stack Builder creates a user scenario for infrastructure manipulation and saves it as a Maestro Stack template. The basis for a stack creation is one of the Primary commands, used to manipulate instances in Cloud.

After a primary command, you can specify additional commands manipulating other resources. These commands will be executed one by one after the primary one succeeds (if other is not specified in the Other option).

Click Catalog to see the list of all stacks available for your project.

Click From Json to paste a ready Maestro Stack Template, CloudFormation or Terraform template .json code.

Stack Builder can be used to create scenarios that would result into the following:

- Running a single command

- Running a chain of commands, and the execution of each next command will start only after the previous one succeeds (no need to check the resources status manually, as is when you work with CLI)

- Running a set of commands simultaneously

- Initiating the creation of an instance (or a specified number of instances) with a number of additional settings (additional storage volumes, specific instance properties, tags).

The saved scenario becomes available in the Run wizard and the users will be able to initiate the scenario execution in just several clicks.

This topic contains the following sections:

Creating a simple stack

To create a simple stack that would run a command and influence a resource in your infrastructure, all you have to do is specify the action you need, and scroll through the Builder by clicking the Next button. The Builder will automatically set the default parameters and make your action universal and customizable. The important thing here is to add a meaningful name to the new stack, as it will be used in the Run wizard stack list, and to specify the correct project to which the Stack Template will be assigned

Stack Commands

Each stack generated by the Builder can contain two types of commands: primary commands and additional commands.

Primary commands are the commands manipulating instances in Cloud. They are the commands that start the stack flow. Any other command, either additional or another primary, is typically executed only after the previous command succeeds.

Additional commands are the commands for manipulating volumes, tags and adding instance properties. Such command is typically used after a primary one.

Execution Modes

There are two ways to organize the order of commands execution in Maestro stacks:

Consecutive: the default mode. Each command is evoked after the execution of the previous one succeeds.

Simultaneous: Several primary commands are evoked automatically, starting several «branches» and the secondary commands in each «branch» are started consecutively.
To switch to the Simultaneous mode, select the Other option on the first step of the Builder.

For more details, please, see our Maestro Stacks Guide, Section "1. General Information".