From ba05620c11e46376f270d2b1549297fa39da2f95 Mon Sep 17 00:00:00 2001 From: shreddedbacon Date: Tue, 16 Jan 2024 10:55:03 +1100 Subject: [PATCH] docs: add global scope documentation --- docs/using-lagoon-advanced/environment-variables.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/using-lagoon-advanced/environment-variables.md b/docs/using-lagoon-advanced/environment-variables.md index f81bf8d3e7..b064413302 100644 --- a/docs/using-lagoon-advanced/environment-variables.md +++ b/docs/using-lagoon-advanced/environment-variables.md @@ -134,6 +134,10 @@ mutation addContainerRegistryEnv { } ``` +### Global Environment Variables \(Lagoon API\) + +Global environment variables are available as both a build-time environment variable so that it may be consumed by builds, and also a runtime variable so that it is available within running containers. + ## Environment Files \(existing directly in the Git Repo\) If you have environment variables that can safely be saved within a Git repository, we suggest adding them directly into the Git repository in an environment file. These variables will also be available within local development environments and are therefore more portable.