Commit 20858889 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 61001132
Loading
Loading
Loading
Loading
+2 −0
Original line number Diff line number Diff line
@@ -181,6 +181,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 `gcloud.env` file in your [deployment script](#deployment-and-cleanup-scripts).

## Configuration reference

### Secrets management
+1 −1
Original line number Diff line number Diff line
@@ -349,7 +349,7 @@ stages:
    else
      echo "$environment_url" > environment_url.txt
    fi
    echo -e "environment_type=$environment_type\\nenvironment_name=$environment_name\\nenvironment_url=$environment_url" > gcloud.env
    echo -e "environment_type=$environment_type\\nenvironment_name=$environment_name\\nenvironment_url=$environment_url" >> gcloud.env
  }

  # environment cleanup function