| `$environment_name` | `{{ env "environment_name" }}` | a generated application name to use for the current deployment environment (ex: `myproject-review-fix-bug-12` or `myproject-staging`). This should be used as **release name** in the `helmfile.yaml` - _details below_ |
| `$environment_type` | `{{ env "environment_type" }}` | the current deployment environment type (`review`, `integration`, `staging` or `production`) |
| `HELMFILE_CLI_IMAGE` | The Docker image used to run helmfile <br/>:warning: **set the version required by your Kubernetes server** | `ghcr.io/helmfile/helmfile:latest` |
| `HELMFILE_PATH` | The path to your `helmfile.yaml` | `./helmfile.yaml` |
@@ -270,7 +270,7 @@ They are **disabled by default** and can be enabled by setting the `HELMFILE_REV
Here are variables supported to configure review environments:
| `TBC_VAULT_IMAGE` | The [Vault Secrets Provider](https://gitlab.com/to-be-continuous/tools/vault-secrets-provider) image to use (can be overridden) | `$CI_REGISTRY/to-be-continuous/tools/vault-secrets-provider:master` |
| `VAULT_BASE_URL` | The Vault server base API url | _none_ |
@@ -382,7 +382,7 @@ Then you may retrieve any of your secret(s) from Vault using the following synta