@collective-intelligence/cli 0.1.3 → 0.1.5
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 +22 -0
- package/dist/cli.js +24 -18
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -20,6 +20,13 @@ bun add -g @collective-intelligence/cli
|
|
|
20
20
|
|
|
21
21
|
Run `ci --help` to check the installation.
|
|
22
22
|
|
|
23
|
+
Run `ci upgrade` to install the latest published version. The command reads the
|
|
24
|
+
latest version from the public npm registry and installs it with the package
|
|
25
|
+
manager that owns the running global install (npm, pnpm or Bun). It changes
|
|
26
|
+
nothing when the running version is the latest one. A `ci` that is a project
|
|
27
|
+
dependency or a source checkout is not a global install: the command fails and
|
|
28
|
+
names the version to install.
|
|
29
|
+
|
|
23
30
|
## Sign In and Enroll Your App
|
|
24
31
|
|
|
25
32
|
Interactive developers sign in once; pipelines keep using a token. Every
|
|
@@ -42,6 +49,12 @@ ci apps enroll \
|
|
|
42
49
|
--redirect-uri <your-app-callback-url> \
|
|
43
50
|
--scopes context:read \
|
|
44
51
|
--env-file .env.local
|
|
52
|
+
|
|
53
|
+
# Read the connection values of an existing application again. This changes
|
|
54
|
+
# nothing in CI. Without --env-file it prints them, for example to copy them
|
|
55
|
+
# into a pipeline's variables.
|
|
56
|
+
ci apps env <your.app.fqn> --env-file .env.local
|
|
57
|
+
ci apps env <your.app.fqn>
|
|
45
58
|
ci logout
|
|
46
59
|
```
|
|
47
60
|
|
|
@@ -74,6 +87,15 @@ ci logout
|
|
|
74
87
|
match the enrolled application; otherwise it fails and asks for
|
|
75
88
|
`--rotate-secret`. It never rotates without `--rotate-secret`. It refuses
|
|
76
89
|
package-owned applications and disabled applications (pass `--enable`).
|
|
90
|
+
- `ci apps env <application>` reads the same output keys for an application
|
|
91
|
+
that already exists; `<application>` is an Application Id or an FQN. It
|
|
92
|
+
accepts the same `--env-file`, `--json` and `--prefix`, and it writes nothing
|
|
93
|
+
to CI. CI shows a client secret only once, so for a confidential application
|
|
94
|
+
the output has no `CI_CLIENT_SECRET` and a note on stderr says so. With
|
|
95
|
+
`--env-file` it keeps an existing `CI_CLIENT_SECRET` when the same file's
|
|
96
|
+
`CI_CLIENT_ID` and `CI_ISSUER` match the application; otherwise it fails and
|
|
97
|
+
writes nothing. To issue a new secret, use `ci apps rotate-secret` or
|
|
98
|
+
`ci apps enroll --rotate-secret`.
|
|
77
99
|
- `ci doctor` checks discovery, the JWKS signing key, Organization access and
|
|
78
100
|
registered redirect URIs; `ci apps enroll` runs the same checks before it
|
|
79
101
|
writes output. Each discovery and JWKS request fails after 30 seconds
|