Adding additional details for debugging about registry pushes

[dgershman]

Description

This enables some additional logging information for pushes to registries.

Related Issue

Relates to #1218

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

• Test, docs, adr added or updated as needed
• Contributor Guide Steps followed

[netlify]

✅ Deploy Preview for zarf-docs canceled.

Name	Link
🔨 Latest commit	8a9bb0c
🔍 Latest deploy log	https://app.netlify.com/sites/zarf-docs/deploys/642db783b6d6b50008c0ce66

[Racer159]

Looks good overall, and thanks for the PR! Requesting this line be added as well since it won't destroy the messages when the spinner completes (if it completes).

Also do you have any log snippets from when you saw the infinite spin with this in place? (was testing locally over this past weekend and while I could significantly slow the Zarf install I never saw it actually infinite spin myself yet).

[dgershman]

Looks good overall, and thanks for the PR! Requesting this line be added as well since it won't destroy the messages when the spinner completes (if it completes).

Also do you have any log snippets from when you saw the infinite spin with this in place? (was testing locally over this past weekend and while I could significantly slow the Zarf install I never saw it actually infinite spin myself yet).

I don't have any logs that I can share, but I can work toward that once this feature is released. Essentially it's not necessarily an infinite spin, but images seem to not push consistently. Sometimes the entire deployment will hang on pushing a small image like gitea or one of the flux images. It will timeout and then retry, sometimes either successfully completing or failing and requiring re-running the whole deployment process.

[Racer159]

Thanks, that is good to know - I was able to see the retry behavior happen in my tests by intentionally killing the connection to trigger them manually (by deleting or otherwise manipulating the registry pod) - what is odd is that is the opposite of what was reported by @corang (and others) #1218 (comment) - more logs will definitely help since this is likely shaping up to be a multi-faceted issue

[Racer159]

lgtm

[dgershman]

Thanks, that is good to know - I was able to see the retry behavior happen in my tests by intentionally killing the connection to trigger them manually (by deleting or otherwise manipulating the registry pod) - what is odd is that is the opposite of what was reported by @corang (and others) #1218 (comment) - more logs will definitely help since this is likely shaping up to be a multi-faceted issue

I started a new ticket to track my findings #1568.