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 (12,822 stars) (1,416 forks)batch import
bugbash/q4-2022help wantedkind/feature-requestpriority/p2tagger/sha256

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

Rename `sha256` tagger to `latest` · GoogleContainerTools/skaffold#5616 | Good First Issue