Automate Helm chart release version bump

[smoya]

Helm charts Chart.yaml file have a field called appVersion where the version of the application running behind should be specified.

Currently, this value is hardcoded to 0.1.0-alpha, but it will be ideal if we can sync it with the release version when bumping a new release.

Meaning, a new release of this repository will also include a version bump on that specific field.

Also, the tag value on the asyncapi-event-gateway helm chart should be in sync with it instead of having latest.

[aniketsat]

Hi @smoya , I am Aniket, a contributor to OpenForce 2022. I would like to work on this issue.

I am new to k8s and helm, can you please guide me how to solve this ?
I would be making a PR as soon as I am done with resolving the issue.

Thank you.

[smoya]

Hi @aniketsat! sorry for the delay but for some reason I didn't see the GH notification.
Thanks for taking the lead on this issue 👍 .

I am new to k8s and helm, can you please guide me how to solve this ?

Actually, you don't really need deep knowledge of K8s and Helm but need to know some concepts.
However, If want to have an idea of what is K8s, and how do you deploy workloads, I recommend you to take a look to https://kubernetes.io/docs/tutorials/#basics.
Same for Helm here https://helm.sh/docs/intro/quickstart.

Regarding the main work we have to do here, It's a bit open. The idea is to find an automated way (if possible) to update the values named in the Issue description during the release process.
As we are using semantic-release, I think we could start by checking this plugin: https://github.com/m1pl/semantic-release-helm. I have some doubts on how to store the changes later on, because I think we would need to commit those during the release process (which is done in this GH Action btw: https://github.com/asyncapi/event-gateway/blob/master/.github/workflows/release.yml.

Regarding the application container image tag (See here, I would say we should find a similar solution.

Do you think you need anything else from me? As I mentioned, this issue implementation is a bit open.

[aniketsat]

Thanks for the explanation @smoya .
I will try to solve this issue.

[derberg]

@aniketsat do you want to continue working on this one? I know OpenForce ended but if you are still interested and you were delayed by exams, we can still give you some time for this one

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️