@topolo/cli 0.1.21 → 0.1.22
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 +33 -2
- package/dist/index.js +1437 -333
- package/package.json +5 -3
package/README.md
CHANGED
|
@@ -10,7 +10,7 @@ via `stdin`/`stdout`.
|
|
|
10
10
|
- Access-token authentication via OAuth device flow when a CLI OAuth client id is configured.
|
|
11
11
|
- Stored access-token refresh when the config includes a refresh token and OAuth client id.
|
|
12
12
|
- First-class `production` and `staging` CLI environments with separate stored credentials, OAuth client ids, and service URL overrides.
|
|
13
|
-
- Commands: `auth login/logout/status`, `whoami`, `apps`, `apps scaffold`, `services`, `crm contacts:list`, `crm contacts:get`, and generic `api` passthrough for SDK-registered services.
|
|
13
|
+
- Commands: `auth login/logout/status`, `whoami`, `apps`, `apps scaffold`, `oauth clients`, `integrations prompt/check`, `services`, `crm contacts:list`, `crm contacts:get`, and generic `api` passthrough for SDK-registered services.
|
|
14
14
|
|
|
15
15
|
## Install
|
|
16
16
|
|
|
@@ -158,11 +158,42 @@ current CLI from source, then runs the local conformance audit with
|
|
|
158
158
|
|
|
159
159
|
For third-party developers, use `--target developer` or `--developer`. Developer
|
|
160
160
|
scaffolds are standalone starter projects with `topolo.app.json`, `.env.example`,
|
|
161
|
-
an
|
|
161
|
+
an `@topolo/login` authorization-code + PKCE browser starter, and no internal TopoloDocs,
|
|
162
162
|
CloudControl, or private first-party package dependencies. Developer scaffolds
|
|
163
163
|
are browser-only by default; add `--with-api` to include a protected Worker
|
|
164
164
|
baseline that validates bearer tokens through Topolo Auth over HTTP.
|
|
165
165
|
|
|
166
|
+
### `topolo oauth clients`
|
|
167
|
+
|
|
168
|
+
Manage OAuth clients for Login with Topolo.
|
|
169
|
+
|
|
170
|
+
```bash
|
|
171
|
+
topolo oauth clients list --json
|
|
172
|
+
topolo oauth clients create \
|
|
173
|
+
--name "Acme App" \
|
|
174
|
+
--developer-id dev_... \
|
|
175
|
+
--redirect-uri https://acme.example.com/auth/topolo/callback \
|
|
176
|
+
--scope openid profile email organization:read entitlements:read \
|
|
177
|
+
--json
|
|
178
|
+
topolo oauth clients rotate-secret oac_... --json
|
|
179
|
+
topolo oauth clients revoke oac_... --json
|
|
180
|
+
```
|
|
181
|
+
|
|
182
|
+
Client revoke disables the developer OAuth client for everyone. User disconnect
|
|
183
|
+
is separate and uses `DELETE /api/developer-oauth/connected-apps/:clientId`.
|
|
184
|
+
|
|
185
|
+
### `topolo integrations`
|
|
186
|
+
|
|
187
|
+
Generate and validate agent handoffs for third-party integrations.
|
|
188
|
+
|
|
189
|
+
```bash
|
|
190
|
+
topolo integrations prompt login-with-topolo --framework auto
|
|
191
|
+
topolo integrations check login-with-topolo --repo-root . --json
|
|
192
|
+
```
|
|
193
|
+
|
|
194
|
+
The Login with Topolo check looks for `@topolo/login`, callback handling,
|
|
195
|
+
required env vars, account-linking fields, and refresh handling.
|
|
196
|
+
|
|
166
197
|
### `topolo api <service> <method> <path>`
|
|
167
198
|
|
|
168
199
|
Escape hatch for endpoints without typed modules yet.
|