provide sylva-core branch information

Today in CI we have two places where we need to know which sylva branch is the relevant one:

  • in the pytest framework, to conditions some test on the sylva branch (e.g. only run test foo for sylva > 1.7, because it can't work on earlier sylva versions) -- this is important, keeping in mind that on an upgrade scenario, today, the CI framework used is the one of the target commit (not the initial commit)
  • in CI deployments, to determine which directory of ci-deployment-values to use
    • today, our code derives this information from the branch name, or when the commit is the commit of an MR the MR target branch
    • but this does not allow to determine what is the relevant sylva branch for the initial branch of an upgrade scenario if this branch isn't a release-x branch
    • for instance a scenario testing an upgrade from fix-foo-sylva-1.7 to main, when the checkout of the fix-foo-sylva-1.7 branch is done there is no clean programatic way to tell that to deploy this branch we need to use the 1.7 directory of ci-deployment-values

All this would be facilitated by ensuring that the sylva-core repository would hold somewhere in a file the information about the sylva branch which is relevant.

This would be then injected in sylva-units-status ConfigMap, to be read from there in the pytest framework

This would be used in our code to cleanly determine the relevant branch in all cases.

Edited by Thomas Morin