Require explicit scope for bakery update files - #753
Open
bschwedler wants to merge 1 commit into
Open
Conversation
bakery update files re-renders every image and version in the project when no --image-name or --image-version filter is given. This is rarely intentional and can silently touch unrelated versions across the whole repo. Add a required --all flag that must be passed explicitly to render everything, mirroring the existing --matrix-versions include/exclude pattern on bakery build. Unscoped calls without --all now fail fast with a clear error instead of defaulting to the widest possible scope.
bschwedler
marked this pull request as ready for review
August 17, 2026 20:34
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #752
Summary
bakery update filesre-rendered every image and version in the project whenever--image-nameand--image-versionwere both omitted, with no warning or confirmation. This adds a required--allflag that must be passed explicitly to render everything, mirroring the existing--matrix-versions include/excludepattern onbakery build. Unscoped calls without--allnow fail fast with a clear error instead of silently defaulting to the widest possible scope. Existing scoped calls are unaffected.Verification
uv run bakery update files(no filters) now exits 1 with "No scope specified...";uv run bakery update files --allrenders every image/version as before. Added BDD scenarios intest/features/cli/update/files.featurecovering both cases; fullpytest test/cli/test_update.pysuite passes.