Skip to content

fix: clarify duckdb command requirements and isolate env/profile config#84

Merged
leonkenneth merged 2 commits into
mainfrom
fix-clarify-duckdb-command-requirements-and-isolate-env-prof
Jul 24, 2026
Merged

fix: clarify duckdb command requirements and isolate env/profile config#84
leonkenneth merged 2 commits into
mainfrom
fix-clarify-duckdb-command-requirements-and-isolate-env-prof

Conversation

@leonkenneth

Copy link
Copy Markdown
Contributor
  • Resolve lakehouse credentials through a single mode-gated resolver so every consumer (auth headers, duckdb's plaintext ATTACH pair, verification) accepts the same sources.
  • Reject incomplete environment configuration at startup (lone lakehouse username or password, endpoint/environment vars without credentials).
  • Refuse explicit --profile / ALTERTABLE_PROFILE selection and altertable logout while environment configuration is active.
  • Never auto-provision lakehouse credentials in env mode; surface an explicit error instead of minting a server-side credential per request.
  • Split altertable duckdb: the no-argument form discovers catalogs through the management API, while altertable duckdb <catalog> attaches directly with lakehouse credentials only.
  • Report an unconfigured management plane as one coherent error via requireManagementPlane (duckdb attach-all, catalogs list/create).

- Resolve lakehouse credentials through a single mode-gated resolver so
  every consumer (auth headers, duckdb's plaintext ATTACH pair,
  verification) accepts the same sources.
- Reject incomplete environment configuration at startup (lone lakehouse
  username or password, endpoint/environment vars without credentials).
- Refuse explicit --profile / ALTERTABLE_PROFILE selection and
  `altertable logout` while environment configuration is active.
- Never auto-provision lakehouse credentials in env mode; surface an
  explicit error instead of minting a server-side credential per request.
- Split `altertable duckdb`: the no-argument form discovers catalogs
  through the management API, while `altertable duckdb <catalog>`
  attaches directly with lakehouse credentials only.
- Report an unconfigured management plane as one coherent error via
  requireManagementPlane (duckdb attach-all, catalogs list/create).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@leonkenneth
leonkenneth enabled auto-merge (squash) July 24, 2026 14:04
@leonkenneth
leonkenneth merged commit b5f6208 into main Jul 24, 2026
12 checks passed
@leonkenneth
leonkenneth deleted the fix-clarify-duckdb-command-requirements-and-isolate-env-prof branch July 24, 2026 14:06
leonkenneth pushed a commit that referenced this pull request Jul 24, 2026
🤖 I have created a release *beep* *boop*
---


##
[1.4.0](v1.3.0...v1.4.0)
(2026-07-24)


### Features

* add `doctor` command for CLI diagnostics
([#79](#79))
([57b1440](57b1440))
* **cli:** simplify the command API surface area
([#75](#75))
([f3a1d4d](f3a1d4d))


### Bug Fixes

* **ci:** enable shell completion verification
([#77](#77))
([db7c52f](db7c52f))
* clarify duckdb command requirements and isolate env/profile config
([#84](#84))
([b5f6208](b5f6208))
* harden transport, JSON fidelity, and profile recovery
([#80](#80))
([facdf90](facdf90))
* keep COMMANDS.md version in sync with release-please
([#87](#87))
([cbb8d65](cbb8d65))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants