Skip to content

Latest commit

 

History

History
186 lines (155 loc) · 5.22 KB

plan.md

File metadata and controls

186 lines (155 loc) · 5.22 KB
Raw

< 📚 Commands Help

✈️ Plan

> rugby plan --help
 > Run sequence of Rugby commands.

 Arguments:
╭──────────────────────────────╮
│ name  * Name of plan to run. │
╰──────────────────────────────╯
 Options:
╭────────────────────────────────────────────────────────────╮
│ -p, --path    * Path to plans yaml. (.rugby/plans.yml)     │
│ -o, --output  * Output mode: fold, multiline, silent, raw. │
╰────────────────────────────────────────────────────────────╯
 Flags:
╭─────────────────────────────────────────────────────────────────────────╮
│ -r, --rollback    * Restore projects state before the last Rugby usage. │
│ -v, --verbose []  * Increase verbosity level.                           │
│ -q, --quiet []    * Decrease verbosity level.                           │
│ -h, --help        * Show help information.                              │
╰─────────────────────────────────────────────────────────────────────────╯

Discussion

The command allows you to write a plan (combination of commands) in YAML format:

cache_plan_name:
- command: warmup
  argument: s3.eu-west-2.amazonaws.com
  headers: 'secret-key: ${RUGBY_S3_SECRET_KEY}'
  except: SomePod
  arch: x86_64
- command: build
  except: SomePod
  arch: x86_64
- command: use
  except: SomePod

It's equal to this sequence of commands:

> rugby warmup s3.eu-west-2.amazonaws.com --except SomePod --arch x86_64
> rugby build --except SomePod --arch x86_64
> rugby use --except SomePod

Then you need to save YAML to .rugby/plans.yml file or in another place.
You can use this command to create a file:

> touch .rugby/plans.yml

Then add to it your plans.


When you are ready, call it using the command plan:

> rugby plan cache_plan_name --path your_plans_file_path

If you save plans to default location .rugby/plans.yml, you can use the shorter command:

> rugby plan cache_plan_name

Or even shorter:

> rugby cache_plan_name

Read more about umbrella command.


Application

You can use 🏈 RugbyPlanner application for visualizing changes in your project without applying them.
It can significantly improve your experience working on your plans.


Several plans

You can write many plans in one file or different ones.
Also, you can use already existing plans in your plans file.

# .rugby/plans.yml
usual:
- command: shell
  argument: pod install
- command: plan
  argument: base # Use base plan from different file
  path: another_path.yml

not_usual: # The second plan
- command: delete
  targets:
  - BrokenPod
  - NotMyTeamTestsPod
- command: plan
  argument: base
  path: another_path.yml
# another_path.yml
base: # The 3rd plan
- command: cache
  except: [SomePod]

And then you can choose which one you need to call:

> rugby not_usual

Or you can call a plan from another file:

> rugby -p another_path.yml

It's not necessary to pass a plan name if it's the first plan in a file.

And also, if you want to call the first plan from the default plans file:

> rugby

Yeah, it's not a mistake. Just call the command without any arguments.


Syntax

Each plans file should be a dictionary where you describe plans names as keys.
The value for each key should be an array with commands.

key1: # It's a plan name
- command: build # It's a command name
- command: use

key2:
- command: shell

Each command can contain arguments, options, and flags.
Arguments should be written in YAML with keyword argument.

usual:
- command: shell
  argument: pod install

For example, the shell command has an argument with the name command.
But you need to change all names of arguments just to the argument keyword.

Options should be written in YAML without prefixes -- and -.
And use only the long version of an option name.

usual:
- command: cache
  arch: x86_64

For example, the cache command has an option arch.
You can't use a: x86_64 in your plans.

Flags should be written in YAML also without prefixes -- and -.
Use only the long version of a flag name. The value should be true or false.

usual:
- command: cache
  strip: true

For example, the cache command has a flag strip.

Plans can access environment variables in two different ways:

usual:
- command: warmup
  argument: s3.eu-west-2.amazonaws.com
  headers: 'secret-key: ${RUGBY_S3_SECRET_KEY}'
  except: $BAD_POD_TARGET_NAME0