Open oraNod opened 2 months ago
Poll for versioning scheme here: https://forum.ansible.com/t/awx-operator-helm-versioning/8228/4
An initial tag was created: https://github.com/ansible-community/awx-operator-helm/releases/tag/24.42.0 which resolves the CI pipeline.
However, we need to map the appVersion
correctly so that 24.42.X
tag from the helm chart can clone the 2.19.X
tags from the awx-operator.
Future versions of the helm chart (e.g. 25.3.X
) should map to new versions of awx-operator only and not to 2.19.X
.
Any ideas on how to do that is welcome.
Current discussion ongoing in the forum about versioning the helm chart: https://forum.ansible.com/t/awx-operator-helm-versioning/8228
The purpose of this issue is to track the discussion so we have a link to the outcome captured somewhere in this repo. If you have comments or input on the versioning, please add your thoughts to the forum topic.
This also relates to https://github.com/ansible-community/awx-operator-helm/issues/7 but that is specific to the borked ci check, which is something we can fix after we figure out the new versioning.