bcdock v0.5.1

bcdock v0.5.1

Beta CLI. Surface and JSON shapes may change between releases - see CHANGELOG.md for what moved.

Install:

go install github.com/bcdock/cli/cmd/bcdock@v0.5.1

Or download an archive below and put the bcdock binary on PATH.

Changes in this release

Fixed

• auth signup says when it did not create your first environment, and why. When the
  invite carries a BC configuration (from the waitlist) or you pass one, signup creates your
  first environment. If that configuration can no longer be created - most often a version
  with no ready image any more - the account is still activated and signup prints
  No environment was created: <reason>, with how to create one (bcdock env create).
  It used to report success and queue an environment that could not start.

Changed

• bcdock auth login keys carry two more scopes: billing:write and account:write. me export,
  me delete and me cancel-deletion now need account:write, and billing checkout / billing portal
  need billing:write, so a key minted for CI with only env:read can no longer delete the account,
  export its data or change the plan. A key from an earlier bcdock auth login lacks the new scopes:
  those commands answer with a 403 that says to run bcdock auth login to refresh your key.
• An API key with only billing:write can no longer read environment data (environments,
  logs, stats, health). Environment reads need env:read or env:write; billing and usage reads
  accept env:read, env:write or billing:write. Keys from bcdock auth login carry env:read,
  so every bcdock command that reads environments, billing or usage works as before.
• The --bc-version help and the auth signup / auth join-waitlist examples use a full
  version (or <version> from bcdock artifacts list --region <r> --fast-only) instead of
  25.5, which the API refuses.

---

Full changelog: CHANGELOG.md
Report issues: support@bcdock.io · Security: see SECURITY.md