Proposal: Permit custom buildCommand to export skaffold ENV vars that could be referenced in later in skaffold.yaml templating

[bitsofinfo]

Permit custom buildCommand to export skaffold ENV vars that could be referenced in Helm releases

Would be great if this:

build:
  artifacts:
    - image: myreg.test.com/my/my-app
      custom: 
        buildCommand: ./builder.sh
...

Could (via STDOUT or other means) convey some variables that Skaffold could add to its execution environment whereby they could be referenced elsewhere in skaffold.yaml, i.e.

deploy:
  helm:
    releases:
      - name: my-app-{{.SOME_VAR_SET_BY_BUILD_CMD}}
        chartPath: bitsofinfo-appdeploy/appdeploy
        remote: true
        version: 1.1.14
...

maybe something like if the process has STDOUT that contains something like

skaffold.setenvvar.SOME_VAR_SET_BY_BUILD_CMD=myvalue

that could be exported into the skaffold environment for reference later on the templating in skaffold.yaml.

Really really could use this!

Azure pipelines has this kind of functionality so this is not unprecedented in the world of cicd.

https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#set-variables-in-scripts

[bitsofinfo]

#1441

[nkubala]

@bitsofinfo yeah pre-deploy hooks immediately came to mind. would that fully address this for you? if so can we close this as a dupe?

[bitsofinfo]

@nkubala, well not really, this ticket is about permitting buildCommands to have a way to declare variables that can be consumed by other skaffold components. related I guess, but i don't see anything in that other original poster's issue about what I am proposing here.

[tejal29]

Reducing priority for the feature.