Commit 15c7238f authored by Pierre Smeyers's avatar Pierre Smeyers
Browse files

feat: allow propagate custom output variables 

The template now allows the deployment script to propagate custom
output variables.
parent 1dbbc836

README.md

+2 −0
Original line number Diff line number Diff line
@@ -179,6 +179,8 @@ Each deployment job produces _output variables_ that are propagated to downstrea 


Those variables may be freely used in downstream jobs (for instance to run acceptance tests against the latest deployed environment).



You may also add and propagate your own custom variables, by pushing them to the `helm.env` file in your [deployment script](#deployment-and-cleanup-scripts).



### Working with repositories & OCI-based registries



The Helm template supports indifferently the use of [chart repositories](https://helm.sh/docs/topics/chart_repository/) and [OCI-based registries](https://helm.sh/docs/topics/registries/) (requires Helm 3 or above).

templates/gitlab-ci-helm.yml

+1 −1
Original line number Diff line number Diff line
@@ -518,7 +518,7 @@ stages: 
    else

      echo "$environment_url" > environment_url.txt

    fi

    echo -e "environment_type=$environment_type\\nenvironment_name=$environment_name\\nenvironment_url=$environment_url" > helm.env

    echo -e "environment_type=$environment_type\\nenvironment_name=$environment_name\\nenvironment_url=$environment_url" >> helm.env

  }



  # delete application (and dependencies)