Skip to content

feat(oci): report progress for OCI pull operations#1321

Merged
emoskito merged 3 commits intomainfrom
1320_progress_pull
Feb 20, 2026
Merged

feat(oci): report progress for OCI pull operations#1321
emoskito merged 3 commits intomainfrom
1320_progress_pull

Conversation

@brandtkeller
Copy link
Copy Markdown
Member

@brandtkeller brandtkeller commented Feb 12, 2026

Description

re-establishes parity with progress on OCI pull operations (bundle/packages) that existed prior to zarf removal of the message package.

Utils code was pulled from previous zarf releases before message package was removed and is generally copy/paste.

Visuals

Before:
image

After (in progress):
Screenshot 2026-02-12 at 1 42 20 PM

After (complete):
Screenshot 2026-02-12 at 1 45 29 PM

Related Issue

Fixes #1320

Relates to #

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Other (security config, docs update, etc)

Checklist before merging

Signed-off-by: Brandt Keller <brandt.keller@defenseunicorns.com>
@brandtkeller brandtkeller self-assigned this Feb 12, 2026
@brandtkeller brandtkeller requested a review from a team as a code owner February 12, 2026 21:39
Signed-off-by: Brandt Keller <brandt.keller@defenseunicorns.com>
Copy link
Copy Markdown
Contributor

@mjnagel mjnagel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe this was the case historically too, but with --no-progress the output is a bit weird:

  •  Pulling: uds-k3d-dev (0.00 Byte of 569.41 MBs)
  ✔  Successfully pulled: uds-k3d-dev (569.41 MBs)

(this is running uds deploy k3d-core-slim-dev:latest --no-progress with a build of this branch)

LGTM overall though.

Edit: In thinking more about it, this seems like the best we can do probably if we want to adhere to no-progress. And I think this is a drop-in restoration of the old functionality so good with it.

@mjnagel
Copy link
Copy Markdown
Contributor

mjnagel commented Feb 12, 2026

Approving - think we may want on merge until we get a separate patch out for the create/optional components bug.

@emoskito emoskito merged commit fc2a023 into main Feb 20, 2026
20 checks passed
@emoskito emoskito deleted the 1320_progress_pull branch February 20, 2026 01:01
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.

re-establish progress bar for OCI pull operations

3 participants