@collective-intelligence/cli 0.1.8 → 0.1.10
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 +48 -0
- package/dist/cli.js +31 -26
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -229,6 +229,54 @@ fields; adoption keys are concrete declaration FQNs. The backend validates
|
|
|
229
229
|
Organization/template/ownership compatibility and keeps credentials in native
|
|
230
230
|
connection custody. Invalid input errors omit input values.
|
|
231
231
|
|
|
232
|
+
Each `ci deploy` invocation evaluates FQN-only dependencies against the catalog's
|
|
233
|
+
latest eligible releases, even for unchanged parent bytes. Install/update keys
|
|
234
|
+
are fresh per invocation; transport retries preserve the admitted operation.
|
|
235
|
+
Before install/update admission, the CLI writes a private recovery receipt and
|
|
236
|
+
prints its path (`kind: "recovery"`, `recoveryFile` in JSON output). Errors also
|
|
237
|
+
include `recoveryFile` once saved. After a lost response, timeout, or process exit,
|
|
238
|
+
resume that admission with:
|
|
239
|
+
|
|
240
|
+
```sh
|
|
241
|
+
ci deploy --backend-url <same-api-base-url> --organization <same-organization> \
|
|
242
|
+
--resume <receipt-file> --json
|
|
243
|
+
```
|
|
244
|
+
|
|
245
|
+
Resume replays the original operation kind, request body and idempotency key,
|
|
246
|
+
without rebuilding, looking up releases, or reconciling changed installation
|
|
247
|
+
state. It authenticates with the same Organization management credential as the original
|
|
248
|
+
invocation and needs no publisher token. A salted credential fingerprint binds
|
|
249
|
+
the receipt to that credential; changed or rotated credentials fail closed before
|
|
250
|
+
replay, even for the same Organization, because Backend idempotency is scoped to
|
|
251
|
+
the authenticated principal. The token itself is never stored.
|
|
252
|
+
The Backend still authorizes the request; a rejected/expired recovery fails and
|
|
253
|
+
never silently starts another operation. Do not combine `--resume` with
|
|
254
|
+
`--declaration`, inputs, variables, Gateway bindings or breaking-change flags.
|
|
255
|
+
A normal deploy without `--resume` always creates a fresh invocation.
|
|
256
|
+
|
|
257
|
+
Receipts are stored under `$XDG_STATE_HOME/ci/deployments`, or
|
|
258
|
+
`$HOME/.local/state/ci/deployments` (the OS home directory if HOME is absent),
|
|
259
|
+
in a private 0700 directory with a 0600 file, synchronously flushed before
|
|
260
|
+
admission. If writing fails, no install/update is submitted. Receipts bind the
|
|
261
|
+
full configured API base URL (including any path), Organization and management
|
|
262
|
+
credential; mismatches,
|
|
263
|
+
malformed files, symbolic links and files accessible to other users are rejected
|
|
264
|
+
before replay. They contain deployment inputs, which may include connection
|
|
265
|
+
credentials, but never management/publisher authentication tokens. Keep them
|
|
266
|
+
private and delete their `deploy-*` directories once recovery is no longer needed.
|
|
267
|
+
The operation can also be inspected using its Operation ID when available.
|
|
268
|
+
Dependency declarations are `dependencies: [{ fqn: "com.acme.base" }]`; the old
|
|
269
|
+
`releaseId`/`releaseDigest` fields are rejected. Existing pinned installations
|
|
270
|
+
need the [staged bridge-release cutover](../../../docs/reference/package-release-cli.md#cut-over-existing-pinned-installations)
|
|
271
|
+
on the old Host before strict rollout; rebuilding/republishing or uninstalling
|
|
272
|
+
alone cannot clear retained old Desired/Serving manifests. Exact IDs/digests remain release metadata and
|
|
273
|
+
accepted backend operation selections; offline builds require no catalog access.
|
|
274
|
+
|
|
275
|
+
Existing concrete deployment checks still apply to catalog selections. A later
|
|
276
|
+
promotion can select a lower semantic version, but strict deployment refuses that
|
|
277
|
+
downgrade and preserves the installed selection. It reports the blocker instead
|
|
278
|
+
of silently falling back to another release.
|
|
279
|
+
|
|
232
280
|
`ci deploy` also accepts `--var <name>=<value>` (repeatable). The value is
|
|
233
281
|
coerced by the declared type: `string` as-is, `number`, `boolean` as `true` or
|
|
234
282
|
`false`, `string[]` comma-separated, `json` parsed. `--var <name>=@<ORG_VARIABLE_KEY>`
|