primcli 3.0.0-preview.3 → 3.0.0-preview.4

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
@@ -71,8 +71,9 @@ primitive listen --subscription local-webhook --forward-to http://localhost:3000
71
71
  ```
72
72
 
73
73
  This mode forwards the exact signed body and existing webhook headers. Configure
74
- the handler with your existing account webhook secret and normal signature
75
- verification. The CLI never forwards your API credentials. It does not follow
74
+ the handler with the secret the webhook signs with (the account webhook secret,
75
+ or the webhook's own secret when its `signed_with` is `own_secret`) and normal
76
+ signature verification. The CLI never forwards your API credentials. It does not follow
76
77
  redirects or disable TLS verification. A response must finish within 30 seconds
77
78
  and remain within 1 MiB. Existing confirmation headers retain their meaning,
78
79
  including account content-discard behavior; exec and stdout do not confirm
@@ -263,7 +264,7 @@ primitive keys revoke <id>
263
264
 
264
265
  Creating, rotating and changing a key run directly. If your organization requires approval, the command prints the approval link, opens it where it can, and waits for the one-time token the page shows. In a script it prints the link and exits: approve, then run it again with `--step-up-token`. The new secret is printed once, alone on stdout (or in the JSON with `--json`), and the CLI never saves it, so store it right away. `keys revoke` asks for confirmation; pass `--yes` in scripts.
265
266
 
266
- `primitive roles list`, `primitive roles groups`, `primitive roles mailbox-access` and `primitive roles access-mode` read roles, groups, mailbox access and the access mode. Where the server has not enabled them, they print `feature_disabled`. The built-in roles are `owner`, `admin`, `operator` and `member`. `operator` has every permission `admin` has except managing members, changing roles, sending invitations and billing. By default, owners, admins and operators may use the CLI. An organization can open it to every member by setting `cli_access` to `all_members` in its credential policy.
267
+ `primitive roles list`, `primitive roles groups`, `primitive roles mailbox-access` and `primitive roles access-mode` read roles, groups, mailbox access and the access mode. `primitive roles members` (also `primitive members list`) lists the members and their roles. Where the server has not enabled them, they print `feature_disabled`. The built-in roles are `owner`, `admin`, `operator` and `member`. `operator` has every permission `admin` has except managing members, changing roles, sending invitations and billing. By default, owners, admins and operators may use the CLI. An organization can open it to every member by setting `cli_access` to `all_members` in its credential policy.
267
268
 
268
269
  ### Trying the preview
269
270