skaffold render does not respect templating deploy.helm.releases.name

[netaskd]

Actual behavior

In the doc (https://skaffold.dev/docs/environment/templating/):

List of fields that support templating:

build.artifacts.[].docker.buildArgs (see builders)
build.tagPolicy.envTemplate.template (see envTemplate tagger)
deploy.helm.releases.setValueTemplates (see Deploying with helm)
deploy.helm.releases.name (see Deploying with helm)    <-----------------------------------------------
deploy.helm.releases.namespace (see Deploying with helm)
deploy.kubectl.defaultNamespace
deploy.kustomize.defaultNamespace

My skaffold.yaml contains:

profiles:
- name: deploy
  deploy:
    helm:
      releases:
      - name: "app-{{.PROJECT_VERSION}}"
        artifactOverrides:
          image: app
...

where PROJECT_VERSION is "0.0.1" (sourced from dev-env file to the current shell env)

So, when I run skaffold render it does not fill variable and shows it as is in the skaffold.yaml. For example, ConfigMap contains:

$ skaffold render
---
# Source: app/templates/configmap/env.yaml
kind: ConfigMap
apiVersion: v1
metadata:
  name: app-{{.PROJECT_VERSION}}-env
  namespace: dev-01
data:
...

This behavior affects all points where I use {{ .Release.Name }} in helm chart. Source ConfigMap looks like this:

kind: ConfigMap
apiVersion: v1
metadata:
  name: {{ .Release.Name }}-env
  namespace: {{ .Values.stand }}
data:
...

Information

• Skaffold version: 1.21
• Operating system: Centos7
• Installed via: skaffold.dev

[briandealwis]

There are a few different forms of templating, and in this situation is referring to Go templating in the skaffold.yaml, not Helm templating. So you can refer to environment variables, but not values from the Helm deployer valuesFiles.

@GoogleContainerTools/skaffold-team thoughts? Are there any dangers in loading the valuesFiles and making them available for templating within Helm templated fields?

[briandealwis]

@netaskd could you clarify:

where PROJECT_VERSION is "0.0.1" (sourced from dev-env file to the current shell env)

Did you mean you were providing PROJECT_VERSION from the environment, or were you looking to retrieve the value from the values files?

[netaskd]

@briandealwis, PROJECT_VERSION providing from environment.

In this example:
The dev-env file contains

export PROJECT_VERSION=0.0.1

then

$ source ./dev-env
$ skaffold render

[briandealwis]

So that should be supported. Could you please run Skaffold with -vdebug to enable debug-level logging, and attach the output here (eliding any confidential information)?

[netaskd]

@briandealwis, log is here:
https://privatebin.net/?603ad1ae12cfe2dd#F2vAwhBNXNvtJ2pQoHMF7ZMWHhfeuDpUgmzTwTM6FWUs

[netaskd]

content app: https://privatebin.net/?7c8da2b648a852db#GfpopT5yAt7y2d9uj273DaFnoHs9BbZNR6n1MFrpe9UL

[netaskd]

@briandealwis looks like the issue exists when set

build.tagPolicy.envTemplate.template: "{{.PROJECT_VERSION}}"