@supercheck/cli 0.1.1-rc.3 → 0.1.2

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.
package/README.md CHANGED
@@ -81,9 +81,11 @@ supercheck upgrade
81
81
  ```bash
82
82
  supercheck job run --id <job-id>
83
83
  # or (CI/CD trigger key flow)
84
- supercheck job trigger <job-id> --wait
84
+ SUPERCHECK_TRIGGER_KEY=sck_trigger_... supercheck job trigger <job-id>
85
85
  ```
86
86
 
87
+ `supercheck job trigger` requires `SUPERCHECK_TRIGGER_KEY`. If you also pass `--wait`, set `SUPERCHECK_TOKEN` so the CLI can poll the resulting run.
88
+
87
89
  ## Command Reference
88
90
 
89
91
  ### Authentication
@@ -108,6 +110,9 @@ supercheck upgrade
108
110
  | `supercheck config print` | Print resolved `supercheck.config.ts` |
109
111
 
110
112
  > Note: In the current API, status pages are readable/deletable from CLI sync flows, but create/update endpoints are not available.
113
+ > Pull preserves non-default status page language values (for example `es`, `fr`) for config visibility.
114
+
115
+ > Note: Self-hosted email/password sign-in is for dashboard access. CLI authentication remains token-based (`supercheck login --token ...`).
111
116
 
112
117
  ### Jobs & Runs
113
118
 
@@ -123,7 +128,7 @@ supercheck upgrade
123
128
  | `supercheck job keys delete <jobId> <keyId>` | Revoke a trigger key |
124
129
  | `supercheck job run --id <job-id>` | Run a job immediately |
125
130
  | `supercheck job run --local` | Run a job locally using local test files |
126
- | `supercheck job trigger <id> --wait` | Trigger a job and wait for completion (CI/CD) |
131
+ | `supercheck job trigger <id> --wait` | Trigger a job with a trigger key and wait for completion (CI/CD) |
127
132
  | `supercheck run list` | List recent execution runs (`--job`, `--status`, `--page`, `--limit`) |
128
133
  | `supercheck run get <id>` | Get run details |
129
134
  | `supercheck run status <id>` | Get run status |
@@ -161,7 +166,7 @@ supercheck upgrade
161
166
 
162
167
  | Command | Description |
163
168
  |---|---|
164
- | `supercheck var list / get / set / delete` | Manage project variables |
169
+ | `supercheck var list / get / set / delete` | Manage project variables (`var set` supports `--value-stdin` for secrets) |
165
170
  | `supercheck tag list / create / delete` | Manage tags |
166
171
  | `supercheck notification list / get / create / update / delete / test` | Manage notification providers |
167
172
  | `supercheck alert history` | View alert history |
@@ -216,9 +221,12 @@ export default defineConfig({
216
221
  - name: Run E2E Tests
217
222
  run: npx @supercheck/cli job trigger ${{ secrets.SUPERCHECK_JOB_ID }} --wait --json
218
223
  env:
224
+ SUPERCHECK_TRIGGER_KEY: ${{ secrets.SUPERCHECK_TRIGGER_KEY }}
219
225
  SUPERCHECK_TOKEN: ${{ secrets.SUPERCHECK_TOKEN }}
220
226
  ```
221
227
 
228
+ `SUPERCHECK_TRIGGER_KEY` is required to start the run. `SUPERCHECK_TOKEN` is only needed here because the example uses `--wait`.
229
+
222
230
  ### GitLab CI
223
231
 
224
232
  ```yaml
@@ -228,6 +236,7 @@ test:
228
236
  - npm install -g @supercheck/cli
229
237
  - supercheck job trigger $SUPERCHECK_JOB_ID --wait
230
238
  variables:
239
+ SUPERCHECK_TRIGGER_KEY: $SUPERCHECK_TRIGGER_KEY
231
240
  SUPERCHECK_TOKEN: $SUPERCHECK_TOKEN
232
241
  ```
233
242
 
@@ -251,9 +260,10 @@ test:
251
260
  | `--json` | Output in JSON format |
252
261
  | `--quiet` | Suppress non-essential output |
253
262
  | `--debug` | Enable debug logging |
254
- | `--config <path>` | Path to config file (for config-aware commands) |
255
263
  | `-v, --version` | Show CLI version |
256
264
 
265
+ Config-aware commands such as `config`, `diff`, `deploy`, `pull`, `validate`, and `destroy` accept `--config <path>`.
266
+
257
267
  ## Links
258
268
 
259
269
  - [Website](https://supercheck.io)