GoogleContainerTools/skaffold

Rename `sha256` tagger to `latest`

Open

#5,616 opened on Mar 29, 2021

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (1,416 forks)batch import
bugbash/q4-2022help wantedkind/feature-requestpriority/p2tagger/sha256

Repository metrics

Stars
 (12,822 stars)
PR merge metrics
 (Avg merge 3d 6h) (16 merged PRs in 30d)

Description

The name of the sha256 tagger incorrectly implies that it generates tag based on the a SHA256 digest of the artifact contents. We should

  • move the sha256 tagger to the end of the list in docs/content/en/docs/pipeline-stages/taggers.md and document that its use is best used only for CD type jobs
  • rename the tagger to latest to avoid any implicit associations, with a skaffold.yaml migration
  • add a #sha256-uses-latest-to-tag-images ref to the doc to explain why it was renamed
  • rename the tagger/sha256 issue label

Contributor guide

Research direction
Locate the sha256 tagger implementation, rename it to 'latest', and update all references including documentation and labels.
Tech stack
go
Domain
devtools
Issue type
Refactor
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.
1-3 hours
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
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75