Encrypted project environment commands
pinset env export
Deliberately export one profile as a plaintext dotenv file for a system that cannot consume Pinset injection.
View source on GitHub ↗| Field | Description |
|---|---|
| Purpose | Deliberately export one profile as a plaintext dotenv file for a system that cannot consume Pinset injection. |
| Syntax and arguments | pinset env export --profile <name> --format dotenv --output <path> --allow-plaintext [--cwd <path>]. dotenv is the only format. |
| Modifies state | Yes. Creates a new plaintext file; it never overwrites an existing path. |
| Example | pinset env export --profile development --format dotenv --output ./local.env --allow-plaintext |
| JSON | No. |
| Key errors | Missing consent flag, existing/unsafe output, permission-hardening failure, missing identity, or invalid ciphertext. |
The output is restricted to the current user (0600 on Unix and a user-only ACL on Windows). It still contains plaintext; do not commit it, and delete it as soon as its explicit use is complete.
/en/docs/commands/env-exportPinset 2.1