Command: ennote secret create
Usage
Create new secrets directly from the terminal. You can pass values via inline flags or pipe data through standard input (stdin) to avoid leaving secrets in your shell history.
ennote secret create <secret-name> [flags]
Examples
# Create a standard login/password secret
ennote secret create "prod-db-credentials" --type LOGIN_PASSWORD --login "admin" --password "supersecret"
# Pipe a .env file directly into a KEYS_VALUES secret
cat .env | ennote secret create "stripe-keys" --type KEYS_VALUES
# Create a 2FA token
ennote secret create "github-2fa" --type TWO_FACTOR --value "JBSWY3DPEHPK3PXP"
# Create a secure note or pipe an SSH key
ennote secret create "arch-notes" --type SECURITY_NOTES --value "Critical infrastructure details"
cat id_rsa | ennote secret create "bastion ssh" --type SECURITY_NOTES
Creation Flags
--type: Type of secret (LOGIN_PASSWORD, KEYS_VALUES, SECURITY_NOTES, TWO_FACTOR).--login: Login username or email.--password: Password payload for the secret.--value: Payload for SECURITY_NOTES or TWO_FACTOR.--labels: Comma-separated list of labels.--notes: Optional metadata description.--url: Associated URL for the secret.
Secret types are described in Secret Types; TWO_FACTOR stores the 2FA secret key used to generate TOTP codes.
Global flags: --organization-id, --workspace-id (ennote secret).
FAQ
How do I create a secret without leaving it in my shell history?
Pipe the value through standard input instead of passing it as a flag, for example cat .env | ennote secret create "stripe-keys" --type KEYS_VALUES.
Need Help?
If you encounter any issues or have questions, don't hesitate to contact support. Our team is here to assist you with any challenges you might face.
Overview
ennote secret is the Ennote CLI command group for secrets: create a secret, import a 1Password, LastPass or Bitwarden export, and read a secret or inject it into a process as environment variables.
get
ennote secret get prints an Ennote secret, a single key or an older version, or injects the secret's keys as environment variables into a child process, so no .env file is written to disk.