GoogleContainerTools/skaffold

Rename `sha256` tagger to `latest`

オープン

#5,616 opened on 2021/03/29

 (0 件のコメント) (0 件のリアクション) (0 人の担当者)Go (1,416 件のフォーク)batch import
bugbash/q4-2022help wantedkind/feature-requestpriority/p2tagger/sha256

Repository metrics

Stars
 (12,822 個のスター)
PR merge metrics
 (平均マージ 3d 6h) (30d で 16 merged PRs)

説明

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

コントリビューターガイド