cloud bootstrap¶

NAME¶

phyware cloud bootstrap — initialise and inspect PhyCloud platform state.

SYNOPSIS¶

phyware cloud bootstrap init   [OPTIONS]
phyware cloud bootstrap status [OPTIONS]

DESCRIPTION¶

init¶

Creates the default admin tenant, admin user, and seed API keys required to operate PhyCloud. Safe to run on an already-bootstrapped instance (idempotent).

status¶

Reports whether the platform has been bootstrapped and whether all required services are healthy.

OPTIONS¶

Flag	Type	Required	Default	Env
`--url`	string	No	`http://localhost:8000`	`PHYCLOUD_URL`
`--api-key`	string	No	—	`PHYCLOUD_API_KEY`
`--output`	enum	No	`table`	—

| --admin-email | string | No | — | — | | --admin-password | string | No | — | — | | --force | bool | No | false | — |

ARGUMENTS¶

None.

INPUT¶

None.

OUTPUT¶

Field	Type	Description
`status`	string	`bootstrapped` / `not_bootstrapped`
`admin_id`	string	Admin user ID (init only)
`healthy`	bool	All services healthy

EXIT CODES¶

Code	Meaning
`0`	Success
`1`	Generic / connection error
`2`	Authentication / authorisation error
`3`	Resource not found
`4`	Validation error
`5`	Server-side error

EXAMPLES¶

# Check bootstrap status
phyware cloud bootstrap status

# Bootstrap with env-provided credentials
PHYCLOUD_URL=http://localhost:8000 phyware cloud bootstrap init

# Force re-bootstrap
phyware cloud bootstrap init --force

# Bootstrap with explicit admin credentials
phyware cloud bootstrap init --admin-email admin@example.com

# Get status as JSON
phyware cloud bootstrap status --output json

AGENT NOTES¶

Run status before init to avoid redundant bootstraps. init is idempotent but may overwrite seed credentials on --force. Requires direct service access (no API key needed for first bootstrap).

ERRORS¶

Code	Message	Remediation
`ALREADY_DONE`	Already bootstrapped	Use `--force` to re-run
`SERVER_ERROR`	Service unavailable	Check PhyCloud service health