blossom profile:create
Create a profile for one Account
Usage
blossom profile:create [--data DATA] [--name NAME] [--login] [--no-browser]
Flags
| Flag | Description |
|---|---|
--data, -d |
YAML or JSON profile data, a path to a data file, or an HTTP(S) URL |
--name |
Optional profile name; defaults to your username |
--login |
Approve in your browser and save login credentials automatically |
--no-browser |
Print the login URL instead of opening a browser |
Examples:
blossom profile:create --login
blossom profile:create --name prod-tung --login
blossom profile:create --login --no-browser
BLOSSOM_API_URL=https://app.blossom88.dev blossom profile:create --name dev-tung --login
blossom profile:create --data profile.yml --login
New profiles default to https://app.blossom88.com, regardless of the selected
profile. Override with BLOSSOM_API_URL or profile.api_url in a data file;
the environment variable takes precedence. The chosen endpoint is saved.
With --login, choose your Account on the approval page. Blossom creates and
saves the login credentials automatically; you do not need to copy a token.
The URL and code are always printed. A browser opens when available locally;
SSH and headless sessions use the printed URL. --no-browser always skips opening.
Omit --name to use your login username. If taken, Blossom chooses tung-2,
tung-3, and so on. Without a username, it uses your email prefix or display
name, falling back to user.
An explicit name must be unused. Existing profiles are never overwritten.
blossom login --new-profile NAME is a shortcut for named browser setup.
Creating a profile does not switch context. Completion prints the exact command to select it, for example:
blossom profile:use --name tung-2
blossom profile:current
For an existing API token, omit --login and use a data file:
profile:
name: production
api_url: https://app.blossom88.com
token: ${BLOSSOM_TOKEN}
# Optional: verify the token belongs to this Account.
# account: account-100
blossom profile:create --data profile.yml
Without token, setup uses browser login. CI requires a token. Existing names
cannot be overwritten; select the profile and run blossom login to renew it.
Settings are saved in ~/.config/blossom/profiles/NAME.yml; login credentials
are stored separately under ~/.config/blossom/credentials/NAME.yml.
Optional profile.location_id must belong to the Account. Without it, regional
commands use the Account default. --location overrides it for one command.