[RenovateBot] - Ensure ArgoCD Chart + .tool-version CLI is bumped in parallel by the same PR

[julianxhokaxhiu]

Issue Type

Enhancement

Description

The Context:
In its current state, this project uses the Renovate Bot app to bump dependencies and update them automatically without human intervention. Although this is useful for long-term maintenance, there are some tweaks required to ensure the ArgoCD dependency is bumped correctly.

The Solution:
We need a special configuration that handles BOTH these cases and ensures they come up under one single PR somehow:

• Bump the ArgoCD chart version which is not the same as ArgoCD itself AND,
• Bump the CLI version following the ArgoCD version defined in the Chart

The main challenge here is to ensure two different managers cooperate ( asdf for .tool-versions and helmv3 for Charts ) accordingly to ensure they both produce a commit under a single PR. It is totally fine to have two different commits under the same PR as we anyway use the Squash and merge strategy.

[julianxhokaxhiu]

Since the last week, I managed to accomplish the following things:

• Added the argocd plugin detection on the asdf manager on the renovate bot mainline code ( feat(manger/asdf): add argocd support renovatebot/renovate#19941 )
• Created a simple repro case to test the aforementioned implementation and to open the door for discussing how to tackle this issue, on a simpler repo ( https://github.com/julianxhokaxhiu/renovate-test )
• Discussed the possibility of having this feature ( or how to achieve it ) on the official renovate discussion board ( How to tell one manager to the use the version of another manager? (helmv3 -> asdf) renovatebot/renovate#19929 )

After all the discussion unfortunately it seems the renovate bot doesn't support this scenario and the team is not really interested in adding this feature ( for now ).

Therefore, after an internal alignment, there were some ideas that were brought to the table. The main idea is to trigger an action workflow that would trigger when either the .tool-versions or the argocd Chart has been changed, but different scenarios could be triggered:

• ( more feasible ) Cross-check that they are both pointing to the same argocd version. If not, fail the CI job, if yes, mark it as successful OR;
• (less feasible) When one of the two is updated, bump the other one

As this is not a high priority per se, we will put it on hold and wait until this issue really happens. If it will, we could pick it up and implement the aforementioned actions.