Is your feature request related to a problem? Please describe
When Zarf deprecated and removed the message package it came at the cost of uds-cli migrating some of the logic to retain operational capability and disabling some features.
One in particular was the progress bar for bundle/package pull operations.
Currently when you perform a uds pull or uds deploy (with an oci source bundle) the terminal does not provide any feedback to the operation occuring in the background. For large bundles/packages and slow connections this can feel like the state is hanging. Debug logs do not indicate anything more than the bundle being "Found".
Describe the solution you'd like
- Given an oci bundle exists
- When a bundle/package is being pulled
- Then a progress bar should indicate state of oci layer pull
Describe alternatives you've considered
leave the logic as is.
Additional context
Instrumenting new logic around structured logging and zarf/oras may be a large lift - I would advocate for backwards parity with what existed previously.
Is your feature request related to a problem? Please describe
When Zarf deprecated and removed the
messagepackage it came at the cost of uds-cli migrating some of the logic to retain operational capability and disabling some features.One in particular was the progress bar for bundle/package pull operations.
Currently when you perform a
uds pulloruds deploy(with an oci source bundle) the terminal does not provide any feedback to the operation occuring in the background. For large bundles/packages and slow connections this can feel like the state is hanging. Debug logs do not indicate anything more than the bundle being "Found".Describe the solution you'd like
Describe alternatives you've considered
leave the logic as is.
Additional context
Instrumenting new logic around structured logging and zarf/oras may be a large lift - I would advocate for backwards parity with what existed previously.