bcdock v0.5.2

bcdock v0.5.2

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.2

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

Changes in this release

Changed

• bcdock auth set-token reads the key from stdin, so it stays out of your shell history
  and the process list: pbpaste | bcdock auth set-token, or run it and paste the key when
  asked. Passing the key as an argument still works but prints a warning, because the key is
  then saved in your shell history.

Fixed

• env hibernate --wait says why a hibernation failed. When a hibernation fails and your
  environment is still running, the environment records the reason. --wait used to exit 1
  with only hibernate failed (status: running); it now prints that reason, for example
  Hibernation failed: <why>; your environment is still running (status: running).
  env wait adds the same reason when an environment settles in a status you did not wait
  for (it still exits 124).

---

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

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

bcdock v0.5.0

bcdock v0.5.0

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.0

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

Changes in this release

Fixed

• A failed environment stops a --wait at once, with the reason, and exits 1. The
  API reports a failure as status error (or failed-debug); the CLI waited for
  failed, which the API never sends. So env create --wait and env resume --wait on a
  failed environment ran to the full timeout (30 minutes) and printed
  timed out (current status: error) without saying why. They now stop at the first poll
  that sees the failure, print the environment's error message, and exit 1.
  env hibernate --wait and env delete --wait do the same; a delete that ends in
  error is no longer reported as a success.
• A refused create says why and what to do. env create with a short version
  (--version 27) printed only error: invalid_input; the API's sentence ("No BC artifact
  for 27 ... Run 'bcdock artifacts list ...'") was dropped. Any error in that shape now
  prints its message.
• A version with no ready image says so. The API refuses it with
  request_version_required and no message, and the CLI printed that code and nothing
  else. It now names the version and the region and says to pick from
  bcdock artifacts list --region <region> --fast-only, or to run bcdock env create
  with no version for the picker. With -o json the error code is unchanged.
• Confirming a platform upgrade on resume gives the CLI command. The API's message
  said "Resubmit with targetVersion"; the CLI now ends it with
  bcdock env resume <env> --version <version> --wait.

Changed

• env wait exits 1, not 124, when the environment fails. Old: an environment
  that reached a failure status you did not ask for was documented as exit 124, and in
  practice the wait ran to --timeout and then exited 124. New: it exits 1 at once,
  with the environment's error message. 124 still means the wait gave up: --timeout
  elapsed, or the environment settled in another status you did not ask for (such as
  hibernated). A wait that asks for --status failed now exits 1 with the reason too,
  since the API never reports failed. To treat a failure as a success, ask for
  --status error.
• Help text and docs name the real statuses: error and failed-debug, not failed.
• Help examples and the --version flag text use full versions (or <version> from
  bcdock artifacts list --region <r> --fast-only) instead of 25.5, which the API
  refuses. The help topics list the error status and give resume as ~7-15 minutes.

---

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

bcdock v0.4.2

bcdock v0.4.2

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.4.2

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

Changes in this release

Fixed

• --help no longer lists exit codes the CLI never returns. env create,
  env hibernate, env resume, bcdock --help and bcdock help listed 10
  ("provisioning failed") and 2 ("still provisioning"). A failed provisioning,
  hibernate or resume, and a --wait that times out on those commands, exit 1.
  124 is returned when a wait gives up: env wait, or me export --wait. The
  behaviour is unchanged; the help now describes it, matching the exit-codes page.
• env delete --wait exits 0 when the delete succeeds. It used to print
  [deleting] complete (100%), then error: not_found: Environment not found, and exit
  5: once an environment is deleted it is no longer found, and the wait read that as a
  failure. It now prints Deleted. and exits 0. An environment that did not exist
  still exits 5, before anything is deleted.

---

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

bcdock v0.4.1

bcdock v0.4.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.4.1

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

Changes in this release

Changed

• bcdock auth login says where a missing code went. Before the Code: prompt it
  prints No code? Check your Junk or Spam folder., and bcdock auth join-waitlist ends
  with No email? Check your Junk or Spam folder. Some mail providers file BCDock's
  email as junk. Both lines go to stderr; --otp (no one waiting at a prompt) prints
  nothing extra.

---

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

bcdock v0.4.0

bcdock v0.4.0

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.4.0

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

Changes in this release

Added

• With -o json, a failed command writes one JSON object to stderr instead of
  the error: ... line, so a script or an agent can act on the failure without
  parsing text:

  {"error":"invalid_state","message":"invalid_state: Only running environments can be hibernated (current status: hibernated).","exitCode":1,"status":400}
  

  error is the API's own code when it sent one (not_found, invalid_state,
  invalid_input, ...), otherwise one of a small documented set (timeout,
  network, cli_error, and the API's status names). message is the text the
  line would have shown, and status appears only for an API error. The exit code
  is unchanged, stdout stays empty, and table and CSV output keep the text line.
  See the exit-codes page for the full list.

---

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

bcdock v0.3.1

bcdock v0.3.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.3.1

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

Changes in this release

Fixed

• bcdock env create --wait -o json and bcdock env resume -o json now print
  the environment record, the same camelCase object env get -o json returns,
  including id. Before, they printed the table row encoded as JSON: Go field
  names (Name, ShortID, Version, Country, Status, Progress, Region,
  Created) and no id, so a script could not take the environment it had just
  created or resumed and pass it to the next command.

  The same applies to env create --manifest when an app fails to publish: the
  environment exists and is running, and the JSON it prints now carries the id
  you need to re-publish into it or delete it.

  If a script parses those PascalCase keys, update it to the record's keys
  (name, shortId, status, ...), for example jq -r .id. Table and CSV output
  are unchanged.

---

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

bcdock v0.3.0

bcdock v0.3.0

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.3.0

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

Changes in this release

• DEV-088 follow-up: the live smoke found a false entity set in merged text (e95ec0c)
• DEV-088: bcdock env query - the agent's read path into a BC environment (a96686a)
• docs(cli): [Unreleased] -> [0.2.0], now that cli/v0.2.0 exists (87767da)

---

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

bcdock v0.2.0

bcdock v0.2.0

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.2.0

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

Changes in this release

• docs(cli): changelog entry for --manifest, and repair the dead version links (5b00128)
• SEC-039: BC credentials leave the detail read; one audited reveal is the only path to them (e0b4508)
• feat(DEV-024): bcdock env create --manifest - declarative environment recipes (v1) (7c6b90a)
• feat(billing): per-company admin overrides for env quota + trial budget (BILLING-002) (29c0e38)
• feat(cli+smoke): bcdockadm envs suspend/unsuspend + L3 enforcement smoke (BUG-014/ADR-027 PR2) (80fd702)

---

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

bcdock v0.1.3

bcdock v0.1.3

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.1.3

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

Changes in this release

• fix(cli-release): stop goreleaser check gating releases on the deprecated brews: key (eaf1064)

---

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