otty / dotfiles

All tools/Twilio CLI

Twilio CLI

twilio

Unleash the power of Twilio from your command prompt.

Detected by twilio | macOS, Linux, Windows |www.twilio.com

Sync it twilio.toml

Sync rules

What travels, what stays, what never leaves

Twilio CLI in your home directory Every rule on this page, by file

profiles.*.apiKeyprofiles.*.apiSecret

Lifted into your secret store; the rest of the file syncs.

profiles.*.apiKeyprofiles.*.apiSecret

Lifted into your secret store; the rest of the file syncs.

Only what the catalog names. A directory that syncs brings everything inside it except what is listed as excluded here.

apps/twilio.tomlThe file this page is generated from

id = "twilio"

name = "Twilio CLI"

homepage = "https://www.twilio.com/docs/twilio-cli"

description = "Unleash the power of Twilio from your command prompt."

icon = "theSVG:twilio"

detect = ["twilio"]

# twilio-cli's bin/run calls `require('@twilio/cli-core').configureEnv()`

# before oclif starts, and cli-core's src/services/env.js is:

# const home = process.env.HOME || process.env.USERPROFILE || os.homedir();

# const twilioDir = path.join(home, `.${CLI_NAME}`); // CLI_NAME = 'twilio-cli'

# ['TWILIO_CACHE_DIR', 'TWILIO_CONFIG_DIR', 'TWILIO_DATA_DIR']

# .forEach(v => { if (!process.env[v]) process.env[v] = twilioDir; });

# so oclif's config directory is ~/.twilio-cli, and cli-core's

# src/services/config.js puts `config.json` inside it. On Windows that same

# join lands under the user profile, which is what "~/" resolves to here.

# ARCHITECTURE.md says where it used to be: "Profile configuration data is

# stored in ~/.twilio-cli (moved from the preferred ~/.config/twilio-cli)" —

# the oclif default, listed second so an unmigrated machine is still covered.

paths = [

"~/.twilio-cli/config.json",

"~/.config/twilio-cli/config.json",

]

exclude = []

# config.json is not a whole-file secret: the account SIDs, region, edge, the

# active profile and the answered prompts are worth syncing. Only the key pair

# below comes out.

secret = []

# ARCHITECTURE.md: "we prompt them for their Account SID and Auth Token. Using

# these, we create an API key for them and save it directly in the config file

# instead of the system keychain ... This was done to support platforms

# without a keychain". The saved pair is apiKey + apiSecret per profile

# (src/services/config.js, ConfigDataProfile). apiSecret is the password half;

# apiKey is marked too because the pair is useless apart and over-marking

# costs only convenience. Both spellings are named, or the credential is

# lifted out on a migrated machine and syncs in the clear from an old one.

[[secret_paths]]

file = ["~/.twilio-cli/config.json", "~/.config/twilio-cli/config.json"]

match = { key_path = ["profiles.*.apiKey", "profiles.*.apiSecret"] }

Use it with your dotfile manager

Same data, in the shape your tool already reads

Opens Otty and adds this tool to what it syncs

Opens otty://sync/add/twilio. Otty ships with this catalog, so the link only has to name the tool — nothing is downloaded.

Every one of these is generated from the same rules as this page.