параметризовать ?
werf converge —project <APP_NAME>
в одном общем репо держим 1 хельм чарт и деплоим с разными именами (разные микросервисы)
project: {{ env "MY_PROJECT_NAME" }}
$ env | grep MY_PROJECT_NAME MY_PROJECT_NAME=ada Version: v2.10.7 Running time 0.14 seconds Error: unable to load werf config: template: werfConfig:2:12: executing "werfConfig" at <env "MY_PROJECT_NAME">: error calling env: the configuration with potential external dependency found in the werf config: env name "MY_PROJECT_NAME" not allowed by giterminism The use of the function env complicates the sharing and reproducibility of the configuration in CI jobs and among developers, because the value of the environment variable affects the final digest of built images. To provide a strong guarantee of reproducibility, werf reads the configuration and build's context files from the project git repository, and eliminates external dependencies. We strongly recommend following this approach, but if necessary, you can allow the reading of specific files directly from the file system and enable the features that require careful use.
Для вашей задачи вам нужно параметризировать release-name, разве нет?
ну да, чем отличается тогда project от release-name ?
https://werf.io/docs/v2/usage/deploy/releases.html#changing-the-release-name-pattern-werf-only
Обсуждают сегодня