Use a Project Nebula workflow to define the steps in your deployment.
Nebula workflows use
three top-level keys:
version: A string. Your workflow version.
description: A string. A short description of your workflow.
version: v1 description: This workflow prints out a hello message to the logs. It also runs some simple terminal commands and prints their results to the logs.
steps key makes up the body of your workflow. Each step
consists of a
spec key, and an optional
name: A string. The name of the step.
image: A string. The container image and tag you're using for the step.
spec: Use the specification section to define the task that the step is performing. The contents of
specdepends on the task's context. For example, a step that uses the Jira resolve step container to close a Jira ticket must include a
issuekeys. For a list of step containers curated by Puppet see step containers.
dependsOn: (Optional) A list of strings. Use if the step depends on another step in the workflow. This key is useful if you need to set an explicit sequential order for your steps. If you leave out
dependsOn, Nebula executes all of the steps in your workflow simultaneously.
dependsOn: - deploy_test_cluster
version: v1 description: Workflow to echo a nice hello world message to the logs steps: - name: echo image: alpine:latest input: - echo "Hello world. I am $(whoami)" - cat /nebula/spec.json spec: hello: world - name: ls image: alpine:latest command: ls args: - "-la" - "/" dependsOn: - echo - name: ps image: alpine:latest command: ps args: - "-a" dependsOn: - echo
commandkeys still function, but are deprecated. We're working on updating this page with a better example.
Once you've created your workflow, add it to your Nebula account using the web interface or the CLI.