GoogleContainerTools / GoogleContainerTools/skaffold
Rename `sha256` tagger to `latest`
Open
bugbash/q4-2022
help wanted
kind/feature-request
priority/p2
tagger/sha256
- Dominant language
- Go
- Stars
- 15.9k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 10
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
Assessment
This issue has not been assessed yet.