carvel-dev / carvel-dev/secretgen-controller
Improve release process to handle multiple tags on same commit
- Dominant language
- Go
- Stars
- 201
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
**What steps did you take:**
Triggered a tag `t1` on commit `x` and for some reason release action did not pass.
Triggered a new tag `t2` on commit `x` and now release action passed and uploaded artefacts in draft release, but these artifacts have wrong info like tag. It is publishing file like release.yaml and package.yaml with tag `t1` instead of `t2`.
**What happened:**
[A small description of the issue]
**What did you expect:**
It should always pick latest tag that is `t2`
**Anything else you would like to add:**
[Additional information that will assist in solving the issue.]
**Environment:**
- secretgen-controller version (execute `kubectl get deployment -n secretgen-controller secretgen-controller -o yaml` and the annotation is `kbld.k14s.io/images`):
- Kubernetes version (use `kubectl version`)
---
Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.
Contributor guide
Assessment
This issue has not been assessed yet.