Skip to content

docs: address remaining #739 documentation updates - #768

Open
ianpittwood wants to merge 1 commit into
fix/739-metadata-single-platformfrom
fix/739-docs
Open

docs: address remaining #739 documentation updates#768
ianpittwood wants to merge 1 commit into
fix/739-metadata-single-platformfrom
fix/739-docs

Conversation

@ianpittwood

Copy link
Copy Markdown
Contributor

What

Stacked on #767. Closes the remaining documentation gaps in #739 (docs/help only — no logic changes).

Changes

  • imagetools merge help — no longer claims input is produced by
    bakery build --strategy build; reworded to "produced by bakery build --metadata-file (either build strategy)", since either strategy now emits the
    same contract.
  • build --metadata-file help — documents that entries are keyed by
    image-target UID and the write semantics: with --strategy build the file is
    written only after all targets succeed; with --strategy bake buildx owns
    the file.
  • build --plan help — notes it is bake-only and errors out under
    --strategy build.
  • docs/index.qmd — new "Build Strategies" section consolidating the
    strategy differences (parallelism, --plan, --fail-fast scope, metadata
    write semantics) in one discoverable place, plus the
    one-platform-per-invocation constraint and its two concrete consumer
    consequences (dgoss digest fallback, imagetools merge source loss).

Acceptance criteria (#739)

  • No remaining doc/help text implies metadata files are --strategy build-only.
  • Strategy differences documented in one discoverable place (docs/index.qmd).
  • One-platform-per-invocation constraint + its two consequences documented alongside --metadata-file.

Base

Targets fix/739-metadata-single-platform (#767). Rebase onto main once #767 merges.

Refs #739

…739)

Follow-up to the --metadata-file single-platform guard, closing the remaining
documentation gaps from #739:

- imagetools merge help no longer claims input is `--strategy build`-only; both
  strategies produce valid `--metadata-file` input.
- build --metadata-file help documents per-UID keying and the write semantics
  (build: after all targets succeed; bake: buildx owns the file).
- build --plan help notes it is bake-only and errors under --strategy build.
- New "Build Strategies" section in docs/index.qmd consolidates strategy
  differences (parallelism, --plan, --fail-fast scope, metadata write
  semantics) and documents the one-platform-per-invocation constraint plus its
  two concrete consumer consequences (dgoss digest fallback, merge source loss).

Refs #739
@github-actions

Copy link
Copy Markdown

Test Results

2 248 tests   - 2   2 248 ✅  - 2   7m 45s ⏱️ ±0s
    1 suites ±0       0 💤 ±0 
    1 files   ±0       0 ❌ ±0 

Results for commit 611a42a. ± Comparison against base commit d049ce6.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants