lhc configure
Manage CLI profiles. Each profile stores an endpoint URL and an API key for a specific Lakehousecat instance.
Commands
configure
Create or update a profile interactively:
lhc configure [--profile <name>]
| Flag | Default | Description |
|---|---|---|
--profile | default | Name of the profile to create or update |
--ca-cert <path> | (none) | Path to a PEM certificate to trust for this profile's endpoint. Use this for instances running with a self-signed TLS certificate, as an alternative to passing --insecure on every command. |
Example session:
Configuring profile [default]
Endpoint (e.g. https://my.lakehousecat.com): https://acme.lakehousecat.com
API Key: lhc-...
Profile [default] configured.
The endpoint is stored in ~/.lhc/config and the API key in ~/.lhc/credentials (mode 0600).
Passing --ca-cert writes the certificate path to the profile's ca_cert entry in ~/.lhc/config
in the same step:
lhc configure --profile staging --ca-cert ./staging-cert.pem
Once a profile has ca_cert configured, every command run against that profile automatically
trusts that certificate — no need to repeat --ca-cert on each call. Passing --ca-cert on an
individual command still overrides the profile's stored value for that call.
--ca-cert and --insecure are mutually exclusive: configuring a profile with ca_cert and then
also passing --insecure against it results in an error, since the two options represent opposite
trust models (verify a known certificate vs. skip verification entirely).
configure list
List all configured profiles:
lhc configure list
Example output:
PROFILE ENDPOINT CA_CERT
default https://acme.lakehousecat.com
staging https://staging.lakehousecat.com ./staging-cert.pem
The CA_CERT column shows the trusted certificate path for profiles configured with --ca-cert,
and is empty for profiles without one.
Profile Storage
| File | Contents | Permissions |
|---|---|---|
~/.lhc/config | Endpoint and optional ca_cert per profile | 0644 |
~/.lhc/credentials | API key per profile | 0600 |
Both files use INI format. Multiple profiles are stored as INI sections. The default profile is stored in the default (unnamed) INI section.
Environment Variable
Set LHC_PROFILE to select a profile without using --profile:
export LHC_PROFILE=staging
lhc instance info # uses the staging profile