GezimSejdiu commented on PR #170: URL: https://github.com/apache/flink-kubernetes-operator/pull/170#issuecomment-1105752453
> If the helm chart-releaser could support snapshot override, then this PR makes sense to me. Because users could test the new version easily. Indeed. That would be quite beneficial and also the steps you just listed on how to use the SNAPSHOT would be just great that we can already test/use the release (SNAPSHOT) before doing a proper release. From what I can see and also looked into some discussions at https://github.com/helm/chart-releaser-action -- overriding the release doesn't seem supported :( and in our case, the skip flag doesn't really make sense (we want to have a continuous deployment of the SNAPSHOT, right). I can think of a workaround/scenario how to achieve this 'override' the release: - move the default branch to `develop` so that it is obvious it is a SNAPSHOT branch and thus every merge to develop will mean will release a SNAPSHOT and add a step in the workflow that deletes the actual release (if present) as it generates it via: `"{{.Name }}-{{.Version }}"` and then when merged to the main/master branch we have to avoid this step and consider that as a proper release (or even do not let it run for main as anyway the process you seem to follow is by doing a manual release process, and therefore we will not interfere with the main/official release) What do you think of this idea? Do you think it is feasible? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
