CLI Reference

whatalo env

Pull environment variables from the portal to your local .env file, or display them in the terminal.

Subcommands

SubcommandDescription
whatalo env pullDownload variables and write to .env
whatalo env showDisplay variables in the terminal (no file write)

whatalo env pull

Downloads your plugin's environment variables from the portal and writes them to .env in the project directory.

Syntax

whatalo env pull [options]

Options

FlagTypeDescription
--jsonbooleanOutput as JSON instead of writing to file
--path <dir>stringCustom project directory (default: current directory)
--portal-url <url>stringDeveloper Portal URL

Variables written

VariableDescription
WHATALO_CLIENT_IDYour plugin's client ID
WHATALO_PORTAL_URLPortal URL
WHATALO_WEBHOOK_URLWebhook endpoint URL (only if configured)

Note: WHATALO_API_KEY is not included in env pull. It is auto-provisioned by whatalo dev as a store-scoped test key.

Existing variables are preserved. Only Whatalo-specific keys are overwritten. Any other variables already in your .env are left untouched.

Sensitive values are masked in output. Keys containing KEY or SECRET are shown as **** in the terminal confirmation — the actual values are written correctly to the file.

Example

whatalo env pull

Output:

  Writing environment variables to .env

  WHATALO_CLIENT_ID=plugin_01h...
  WHATALO_PORTAL_URL=https://developers.whatalo.com
  WHATALO_WEBHOOK_URL=https://my-plugin.example.com/webhooks/whatalo

  Done.

whatalo env show

Displays your plugin's environment variables in the terminal. Never writes to disk.

Syntax

whatalo env show [options]

Options

Same as env pull:

FlagTypeDescription
--jsonbooleanOutput as JSON
--path <dir>stringCustom project directory
--portal-url <url>stringDeveloper Portal URL

Example

whatalo env show --json
{
  "WHATALO_CLIENT_ID": "plugin_01h...",
  "WHATALO_PORTAL_URL": "https://developers.whatalo.com",
  "WHATALO_WEBHOOK_URL": "https://my-plugin.example.com/webhooks/whatalo"
}

When to use each

Use caseCommand
First-time setup on a new machineenv pull
Onboarding a new team memberenv pull
Verify what variables are configuredenv show
Pipe values into a scriptenv show --json

On this page