envtab (envt\t)

envtab aims to be your goto tool for working with environment variables. Organize sets of environment variables into loadouts. A loadout is a collection of environment variables that can be exported into the shell. Loadouts are named, optionally tagged, and can include a description. envtab stores these loadouts in your $HOME directory (~/.envtab), by default.

envtab loadouts can also be enabled on shell login.

Usage

Take control of your environment.

Usage:
  envtab [command]

Available Commands:
  add         Add an entry to a envtab loadout
  cat         Concatenate envtab loadouts to stdout
  completion  Generate the autocompletion script for the specified shell
  edit        Edit envtab loadout
  export      Export envtab loadout
  help        Help about any command
  login       Export all login loadouts
  ls          List all envtab loadouts
  mk          Make loadout from a template
  rm          Remove envtab loadout(s)
  show        Show active loadouts

Flags:
  -h, --help      help for envtab
  -v, --version   version for envtab

Use "envtab [command] --help" for more information about a command.

To export a loadout into your current shell.

$ $(envtab export aws-prd)
$ envtab show
aws-dev ------------------------------------------------------------- [ 1 / 3 ]
   AWS_DEFAULT_REGION=us-west-2

aws-prd ------------------------------------------------------------- [ 3 / 3 ]
   AWS_ACCESS_KEY_ID=AKIAIOSFODNN7EXAMPLE
   AWS_DEFAULT_REGION=us-west-2
   AWS_SECRET_ACCESS_KEY=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY

Note: The same key pair value can be set in different loadouts. envtab shows each matching loadout.

To show the current state of login (enabled|disabled).

$ envtab login --status
enabled

To enable envtab to export all login loadouts.

envtab login --enable

To remove envtab from login shells.

envtab login --disable

Environment Variables in Values

Sometimes you may need to utilize environment variables in the value of a loadout entry. For example, the PATH environment variable.

CAUTION: To utilize multiple entries of the same KEY (e.g. PATH); you must utilize multiple loadouts. A single loadout cannot have duplicate keys.

add

If you utilize add, the environment variable will be subjected to shell variable/parameter expansion.

$ envtab add testld PATH=$PATH:/other/bin
...
DEBUG: Name: testld, Key: PATH, Value: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/go/bin:/other/bin, tags: [].
...

edit

By editing the loadout configuration directly you can add the environment variable to the entry you need.

$ envtab edit testld
----
metadata:
  createdAt: "2025-11-21T19:21:06-05:00"
  loadedAt: "2025-11-21T19:21:06-05:00"
  updatedAt: "2025-11-21T19:25:07-05:00"
  login: false
  tags: []
  description: ""
entries:
  PATH: $PATH:/other/bin

$ envtab export testld
export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/go/bin:/other/bin

$ $(envtab export testld)
$ envtab show
testld -------------------------------------------------------------- [ 1 / 1 ]
   PATH=$PATH:/some/bin

TODO

• Implement -s|--sensitive option to the addCmd to optionally encrypt values.
  • Support: GCP KMS, AWS KMS, GPG(PGP)
  • Piggy back off sops? It already supports all providers
• In edit subcommand, ensure no duplicate keys (otherwise it will be overwritten)
• Create templates for most commonly used tools.
  • AWS, Vault, etc
  • Check for predefined if no user defined templates match.
• Add additional backends.
  • File (Default)
  • Vault
• Add ability to import/export various backends

Done

• Allow passing filter/pattern arg to the listCmd. (done w/ glob)
• Add support for PATH environemnt variable (done)
• Fix show for PATH environment variable (done)
• Fix Active/Total spacing in ls output when counts are double, or triple digits. (done)