blissful-infra use
Most commands need to know which tenant and project you mean. use sets that once and stores it, so you can type blissful-infra deploy orders instead of blissful-infra deploy orders --tenant acme --project shop.
blissful-infra use acme/shopblissful-infra use [target]| Argument | Meaning |
|---|---|
<tenant> | Set the tenant, leave the project unset |
<tenant>/<project> | Set both |
| (omitted) | Print the current context |
Options
Section titled “Options”| Flag | What it does |
|---|---|
--clear | Clear the stored context |
Examples
Section titled “Examples”blissful-infra use acme # tenant onlyblissful-infra use acme/shop # tenant and projectblissful-infra use # show what is currently setblissful-infra use --clear # forget itHow resolution works
Section titled “How resolution works”Commands that take tenant/project coordinates resolve them in this order:
- An explicit
--tenant/--projectflag on the command - The context stored by
use - For some commands, a registry scan: if exactly one project contains the named service, it is used
This means an explicit flag always wins, so you can reach across to another tenant for a single command without disturbing your context:
blissful-infra use acme/shopblissful-infra status --tenant other-tenant # one-shot, context unchangedThe context is stored in ~/.blissful-infra/context.json.