should the pull logs be classified with INFO?
hellt opened this issue · comments
Currently verbose pull logging (the verbosiness is likely due to the non interactive way the logs are displayed)
But nevertheless, it seems that this pull logs might be rather classified as DEBUG?
INFO | clabernetes | ghcr.io/srl-labs/alpine:latest: resolving |--------------------------------------| │
│ elapsed: 0.5 s total: 0.0 B (0.0 B/s) │
│ │
│ INFO | clabernetes | ghcr.io/srl-labs/alpine:latest: resolving |--------------------------------------| │
│ elapsed: 0.6 s total: 0.0 B (0.0 B/s) │
│ │
│ INFO | clabernetes | ghcr.io/srl-labs/alpine:latest: resolved |++++++++++++++++++++++ │
│ manifest-sha256:388d48147d080f5d2a2dceb82d9054b65b8e6762111703e78ca5cd625487a691: exists |++++++++++++++++++++++++++++++++++++++|
all the stuff that is shell'd out to is put in info rn, so I was just continuing that trend to be consistent, but yea we can put the pull crap into debug if ya want
we can live with that for sure, it just takes a lot of screen estate. We can have this parked for a little while so that it is logged and messes up with the OCD