1ctl profile
1ctl profile manages named API endpoints and credentials so environments or
accounts remain isolated from each other.
Each profile is stored at ~/.satusky/profiles/<name>.json.
~/.satusky/context.json stores only the active profile name.
1ctl profile| Flag | Type | Required | Default | Description |
|---|---|---|---|---|
--help, -h |
boolean | No | — | Show help |
Subcommands
Section titled “Subcommands”| Command | Description |
|---|---|
list |
List all profiles |
create |
Create a new profile |
use |
Switch to a profile |
current |
Show the active profile |
delete |
Delete a profile |
Per-command profile override
Section titled “Per-command profile override”Use --profile (or -p) for one command without changing the active profile:
1ctl --profile staging deployEnvironment variable override
Section titled “Environment variable override”Set SATUSKY_PROFILE to select a profile for a shell session or script:
export SATUSKY_PROFILE=staging1ctl deployAn explicit --profile value takes precedence over SATUSKY_PROFILE, which
takes precedence over the active profile.
Typical multi-environment setup
Section titled “Typical multi-environment setup”1ctl profile create dev --url https://dev-api.satusky.com/v1/cli1ctl profile create prod --url https://api.satusky.com/v1/cli
1ctl profile use dev1ctl auth login --token <dev-token>
1ctl profile use prod1ctl auth login --token <prod-token>
1ctl profile use dev1ctl deploy
1ctl --profile prod deploy