pinset env access request
Generate a public request so a maintainer can authorize this machine or CI to read encrypted profiles.
View source on GitHub ↗When to use
Use for a collaborator's or CI's first access. Requests alone grant nothing; maintainers must env access grant.
Examples
pinset env access request
Result: prints a public request and JSON path. Share the file, retain the identity locally. For CI, run interactive pinset env access request --ci and store the once-displayed identity in a platform Secret.
Behavior
No network access. Public requests go under Pinset home; normal identities use the system credential store or an explicit identity. --ci requires stdin/stdout TTYs, rejects --json, and writes no private-key file. CI can later supply its Secret through PINSET_IDENTITY.
Parameters, exit codes and common errors
| Parameter | Meaning |
|---|---|
--new | Create a new normal identity request. |
--ci | Create a separate CI identity, showing its secret once interactively; conflicts with --new. |
Success exits 0; failure exits 1. PINSET_CI_IDENTITY_TTY requires an interactive terminal without private-output redirection. Conflicting arguments exit 2.