Is your feature request related to a problem? Please describe
When running UDS commands that do things (create, deploy, run to name a few), a very jarring NOTE: is output regarding both UDS and Zarf logs.
Examples:
uds-deploy:
uds-run:
The logs can contain useful information I'm sure but the highlighted NOTE: is very in-your-face (or "loud"?) about logs that do not actually exist yet or if they do, do not contain anything other than the same lines describing where the file exists.
Describe the solution you'd like
Given a command is invoked that would produce meaningful logs
When said command takes action (after confirmation, etc.)
Then logs are recorded unchanged from today, however the log location is not shared until the end of the command invocation. Care should be made to ensure the log locations are still output even if the command errors.
Describe alternatives you've considered
alternatively to only showing log locations at the end, default to only showing them at the end and add a flag to optionally show them at the beginning as well. This would still enable someone to do something like tail -f the logs while the action runs.
Is your feature request related to a problem? Please describe
When running UDS commands that do things (
create
,deploy
,run
to name a few), a very jarringNOTE:
is output regarding both UDS and Zarf logs.Examples:
uds-deploy
:uds-run
:The logs can contain useful information I'm sure but the highlighted
NOTE:
is very in-your-face (or "loud"?) about logs that do not actually exist yet or if they do, do not contain anything other than the same lines describing where the file exists.Describe the solution you'd like
Describe alternatives you've considered
tail -f
the logs while the action runs.