Steps

Go! Deploy

Steps Structure Section

Steps

Step is an operational unit that will be applied with a gneeric client to given hosts.

The Step may contains executable units fragment list known as steps fragment and multiple feeds is like a worksheet that contains other steps, more imported steps (fragment steps files->OptionSet)

Steps fragment files

Sub Step fragment file list is included in the step as sub execution in the point where the include step is placed.

name: Deploy sample commands
group: default
steps:
- name: Include expands and execute more Steps here
  include:
  - strps/sub-steps1.yaml
  - strps/sub-steps2.json
  - strps/sub-steps3.xml

More Feed files

More Feeds file list is importedd in the step as sub execution in the point where the importer step is placed.

name: Deploy sample commands
group: default
steps:
- name: Import and execute more Feeds here
  import:
  - feeds/sub-feed1.yaml
  - feeds/sub-feed2.json
  - feeds/sub-feed3.xml

How does the Feed hierarchy works?

Feed structure is hierarchical and accordignly to the declared steps you can import other steps and feeds, as step sub components (steps fragment and other feeds).

See below image for details:

No limits in cycles

Unfortunately but even fortunately there is control to cycles in feed files, however the pro is that there is not limit to neated steps and feeds levels, so complex operations or product grousp installation procedures can be collected in libraries (the Feed component)

Guide to available Step types

Here the list of available Step classes:

• Include Steps (Described in Step Fragment files paragraph)

• Import Steps (Described in More Feed files paragraph)

• Shell Command Step

• Transfer Command Step

• Service Command Step

Navigate the site

Come back to the Home Page