Add logging for update fails
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 185
- Forks
- 24
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 5
Description
At the moment it seems Frizbee will just fail silently if it can't get a digest e.g. because of auth or network issues. I think it would be worth logging this to stderr.
For example:
FROM redis:invalid_image_tag
is clearly an image reference, but will just be ignored.
I guess this is the place in the code?
https://github.com/stacklok/frizbee/blob/main/pkg/replacer/replacer.go#L303
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at pkg/replacer/replacer.go around line 303 and trace how an image reference is handled when its digest cannot be retrieved. Use FROM redis:invalid_image_tag to reproduce the silent failure, then verify that auth or network-related digest failures are reported to stderr while valid references retain their existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100