Automigration to helm 3 in werf converge command
When werf-converge command detects existing helm 2 release with the same name it will try to render current release using helm 3 with full validation,
Then if render has been succeeded werf will migrate helm 2 release to a newly created helm 3 release. Old helm 2 release will be removed.
CAUTION!
This operation cannot be undone.
Once werf v1.2 has converted your project to helm 3, it cannot be deployed by werf v1.1 anymore. Werf v1.1 will refuse to deploy your project once helm 3 release has been created.
[config] Add fromYaml function
Available in the werf.yaml and .werf/**/*.tmpl configs.
- fromYAML(str string) (map[string]interface{}, error)
- return error if unmarshalling failed
werf.yaml
...
{{- $values := .Files.Get "werf_values.yaml" | fromYaml -}} // or fromYaml (.Files.Get "werf_values.yaml")
from: {{- $values.image.from }}
werf_values.yaml
image:
from: alpine
Internals and fixes
[git_repo, status] Fix no error handling.
[git_repo, status] Fix the use of service work tree when the repository contains submodules
Status should always be taken for the user's work tree