feat(werf): add application version param support

[drey]

Implements #6390

The current implementation scope:

• Add applicationVersion global param support to werf.yml
• Add applicationVersionFile global param support to werf.yml
• Plain/text, JSON, YAML files can be used as applicationVersionFile params
• Giterminism is enforced for applicationVersionFile param
• Giterminism dev mode is supported for applicationVersionFile param
• Handle corner case when both applicationVersion and applicationVersionFile params are set
• applicationVersion value is available in nelm templates by using $.Values.werf.applicationVersion variable

Inline set application version by applicationVersion param

werf.yaml file content:

project: demo-app
configVersion: 1
applicationVersion: v0.0.1

---
image: backend
dockerfile: backend.Dockerfile

---
image: frontend
dockerfile: frontend.Dockerfile

Set application version by external JSON file

werf.yaml file content:

project: demo-app
configVersion: 1
applicationVersionFile: ./version.json

---
image: backend
dockerfile: backend.Dockerfile

---
image: frontend
dockerfile: frontend.Dockerfile

./version.json file content:

{
    "version": "v0.0.1"
}

Set application version by external YAML file

werf.yaml file content:

project: demo-app
configVersion: 1
applicationVersionFile: ./version.yaml

---
image: backend
dockerfile: backend.Dockerfile

---
image: frontend
dockerfile: frontend.Dockerfile

./version.yaml file content:

version: v0.0.1

Set application version by external plain/text file

werf.yaml file content:

project: demo-app
configVersion: 1
applicationVersionFile: ./version

---
image: backend
dockerfile: backend.Dockerfile

---
image: frontend
dockerfile: frontend.Dockerfile

./version file content:

v0.0.1

[alexey-igrychev]

Hi! Thank you for your work and the proposed solution.

The feature looks useful overall, but there are a few points we need to discuss. For example, using $.Values.werf.applicationVersion feels a bit off from an API perspective. We need this value to be more directly available, for instance, through $.Chart, similar to other global parameters like project name or apiVersion.

We’ll take a pause and will get back to you soon with a proposal to improve your solution.

[ilya-lesikov]

Thanks for you work! After discussion, we decided that the feature should be implemented this way:

# werf.yaml
deploy:
  helmChartConfig:
    appVersion: <app version goes here>

With Go templating capabilities of werf.yaml we can already do this:

    appVersion: {{ env "VERSION" }}

and this:

    appVersion: {{ (.Files.Get "version.yaml" | fromYaml).version }}

and probably this:

    appVersion: {{ (.Files.Get "version.json" | fromJson).version }}

so no need for appVersionFile directives.

This appVersion should override whatever in the appVersion of .helm/Chart.yaml (if anything) and then be exposed in a standard way through $.Chart.AppVersion, since this is standard Helm functionality, but not via $.Values.werf.... In Helm the $.Chart structure mirrors whatever is found in the Chart.yaml (more info). To implement this you might need to do some changes to https://github.com/werf/nelm and maybe https://github.com/werf/3p-helm too.

[drey]

Hi Ilya, thank you for the feedback. I like the idea of using the integrated Go templating capabilities you mentioned. I will dive into nelm and implement the change requested.

[drey]

Done.

PS I found a way to override parent's Chart.yaml appVersion without touching nelm and 3p-helm packages.

[ilya-lesikov]

LGTM, thanks! Can you squash commits and sign them so that this will pass: https://github.com/werf/werf/pull/6439/checks?check_run_id=33876806421

[drey]

Done