stacklok/frizbee

Add logging for update fails

Open

#140 opened on Jun 4, 2024

View on GitHubContributor guide
 (3 comments) (0 reactions) (0 assignees)Go (24 forks)auto 404
P2enhancementgood first issue

Repository metrics

Stars
 (186 stars)
PR merge metrics
 (PR metrics pending)

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

Research direction
Add logging when update fails in replacer.go around line 303. Use the standard log package to write to stderr for errors like image resolution failures.
Tech stack
go
Domain
cli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80