@revturbine/cli 0.2.1 → 0.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +9 -9
  2. package/dist/cli.js +2031 -1599
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -1,13 +1,13 @@
1
1
  # revturbine-cli (`revturbine`)
2
2
 
3
- Verify [RevTurbine](https://www.revturbine.com) **ExportedConfig** files and ship
4
- them to a RevTurbine instance through the Change Set lifecycle — from the
3
+ Verify [RevTurbine](https://revturbine.com) **ExportedConfig** files and ship
4
+ them to a RevTurbine instance through the playbook-version lifecycle — from the
5
5
  terminal, the same operations the in-app Pre-Sales Agent performs.
6
6
 
7
7
  `revturbine` is the command-line counterpart to the RevTurbine control plane. It
8
8
  schema-validates a config offline, authenticates to an instance via the browser
9
- (RFC 8628 device flow), and stages / deploys configs as Change Sets so every
10
- change is reviewable and rollback-able.
9
+ (RFC 8628 device flow), and stages / deploys configs as playbook versions so
10
+ every change is reviewable and rollback-able.
11
11
 
12
12
  ## Install
13
13
 
@@ -29,8 +29,8 @@ revturbine signup # create an account (email + passwor
29
29
  revturbine verify ./export-config.json # schema-validate locally (no network)
30
30
  revturbine login # authorize this machine (device flow)
31
31
  revturbine diff ./export-config.json # dry-run: live config vs local, no writes
32
- revturbine upload ./export-config.json # stage as a draft Change Set
33
- revturbine deploy <change-set-id> # submit → approve → deploy (go live)
32
+ revturbine upload ./export-config.json # stage as a draft playbook version
33
+ revturbine deploy <playbook-version-id> # submit → approve → deploy (go live)
34
34
  ```
35
35
 
36
36
  `revturbine <command> --help` documents every flag.
@@ -43,14 +43,14 @@ revturbine deploy <change-set-id> # submit → approve → deploy (go
43
43
  | `login` / `logout` | Device-flow auth; tokens stored at `~/.revturbine/credentials.json` (mode 0600). |
44
44
  | `verify` | Schema-validate a config offline against the bundled schema. |
45
45
  | `diff` | Non-destructive: download the live config, diff against local, dry-run the import. |
46
- | `upload` | Stage a config as a draft Change Set (`--deploy` to also activate). |
46
+ | `upload` | Stage a config as a draft playbook version (`--deploy` to also activate). |
47
47
  | `deploy` | Activate a staged draft: submit → approve → deploy. |
48
48
  | `validate` | Run config-validation against a staged draft. |
49
49
  | `export` | Download the live config (stdout, or `--save`). |
50
50
  | `status` | Show the active draft and recent releases. |
51
- | `discard` / `rollback` | Archive an open draft / revert a deployed change set. |
51
+ | `discard` / `rollback` | Archive an open draft / revert a deployed playbook version. |
52
52
  | `evaluate` | Run the live config's placement/entitlement decisions for a user context. |
53
- | `preview` | Runtime-impact preview of a draft change set. |
53
+ | `preview` | Runtime-impact preview of a draft playbook version. |
54
54
  | `promote` | Promote a compiled config from one environment to another. |
55
55
 
56
56
  ## Schema validation