diff --git a/core/src/config/base.ts b/core/src/config/base.ts index d052bb75a9..e7e47b7e21 100644 --- a/core/src/config/base.ts +++ b/core/src/config/base.ts @@ -43,11 +43,11 @@ export const noTemplateFields = ["apiVersion", "kind", "type", "name", "internal export const varfileDescription = ` The format of the files is determined by the configured file's extension: +* \`.yaml\`/\`.yml\` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * \`.env\` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* \`.yaml\`/\`.yml\` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * \`.json\` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ `.trim() export type ObjectPath = (string | number)[] diff --git a/docs/reference/action-types/Build/container.md b/docs/reference/action-types/Build/container.md index 98137315ea..925d5de2a2 100644 --- a/docs/reference/action-types/Build/container.md +++ b/docs/reference/action-types/Build/container.md @@ -152,11 +152,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Build/exec.md b/docs/reference/action-types/Build/exec.md index ab9ef461dc..cb9477d236 100644 --- a/docs/reference/action-types/Build/exec.md +++ b/docs/reference/action-types/Build/exec.md @@ -152,11 +152,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Build/jib-container.md b/docs/reference/action-types/Build/jib-container.md index f60976869e..5ed441f3d0 100644 --- a/docs/reference/action-types/Build/jib-container.md +++ b/docs/reference/action-types/Build/jib-container.md @@ -164,11 +164,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Deploy/configmap.md b/docs/reference/action-types/Deploy/configmap.md index 8d63e652a5..3c3d6f835a 100644 --- a/docs/reference/action-types/Deploy/configmap.md +++ b/docs/reference/action-types/Deploy/configmap.md @@ -196,11 +196,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Deploy/container.md b/docs/reference/action-types/Deploy/container.md index 1debe52995..4f61dfe664 100644 --- a/docs/reference/action-types/Deploy/container.md +++ b/docs/reference/action-types/Deploy/container.md @@ -196,11 +196,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Deploy/exec.md b/docs/reference/action-types/Deploy/exec.md index 0d9eb0282e..17fc291d86 100644 --- a/docs/reference/action-types/Deploy/exec.md +++ b/docs/reference/action-types/Deploy/exec.md @@ -194,11 +194,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Deploy/helm.md b/docs/reference/action-types/Deploy/helm.md index bd45e496c4..96c8a7eb4d 100644 --- a/docs/reference/action-types/Deploy/helm.md +++ b/docs/reference/action-types/Deploy/helm.md @@ -198,11 +198,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Deploy/kubernetes.md b/docs/reference/action-types/Deploy/kubernetes.md index 96dde7c1e2..94aeb5714e 100644 --- a/docs/reference/action-types/Deploy/kubernetes.md +++ b/docs/reference/action-types/Deploy/kubernetes.md @@ -200,11 +200,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Deploy/persistentvolumeclaim.md b/docs/reference/action-types/Deploy/persistentvolumeclaim.md index 6b1d1b2fc2..f2af1888b0 100644 --- a/docs/reference/action-types/Deploy/persistentvolumeclaim.md +++ b/docs/reference/action-types/Deploy/persistentvolumeclaim.md @@ -196,11 +196,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Deploy/pulumi.md b/docs/reference/action-types/Deploy/pulumi.md index 19cc7379a4..96486460d1 100644 --- a/docs/reference/action-types/Deploy/pulumi.md +++ b/docs/reference/action-types/Deploy/pulumi.md @@ -198,11 +198,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Deploy/terraform.md b/docs/reference/action-types/Deploy/terraform.md index 3c4b0b8b2b..fde020241e 100644 --- a/docs/reference/action-types/Deploy/terraform.md +++ b/docs/reference/action-types/Deploy/terraform.md @@ -202,11 +202,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Run/container.md b/docs/reference/action-types/Run/container.md index a8a06d23cb..52bead21ba 100644 --- a/docs/reference/action-types/Run/container.md +++ b/docs/reference/action-types/Run/container.md @@ -196,11 +196,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Run/exec.md b/docs/reference/action-types/Run/exec.md index 34d7cb0c12..0df1b97e1b 100644 --- a/docs/reference/action-types/Run/exec.md +++ b/docs/reference/action-types/Run/exec.md @@ -194,11 +194,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Run/helm-pod.md b/docs/reference/action-types/Run/helm-pod.md index fbfd308a53..8bb21b3849 100644 --- a/docs/reference/action-types/Run/helm-pod.md +++ b/docs/reference/action-types/Run/helm-pod.md @@ -196,11 +196,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Run/kubernetes-exec.md b/docs/reference/action-types/Run/kubernetes-exec.md index 201c265771..788f17e42a 100644 --- a/docs/reference/action-types/Run/kubernetes-exec.md +++ b/docs/reference/action-types/Run/kubernetes-exec.md @@ -196,11 +196,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Run/kubernetes-pod.md b/docs/reference/action-types/Run/kubernetes-pod.md index 31dc8113b8..55c4d09f1b 100644 --- a/docs/reference/action-types/Run/kubernetes-pod.md +++ b/docs/reference/action-types/Run/kubernetes-pod.md @@ -196,11 +196,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Test/conftest-helm.md b/docs/reference/action-types/Test/conftest-helm.md index 4d4618da31..ffc81e6eaf 100644 --- a/docs/reference/action-types/Test/conftest-helm.md +++ b/docs/reference/action-types/Test/conftest-helm.md @@ -200,11 +200,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Test/conftest.md b/docs/reference/action-types/Test/conftest.md index 19d93cb1ca..962cf62fc4 100644 --- a/docs/reference/action-types/Test/conftest.md +++ b/docs/reference/action-types/Test/conftest.md @@ -198,11 +198,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Test/container.md b/docs/reference/action-types/Test/container.md index eecad90681..20ad7de1d5 100644 --- a/docs/reference/action-types/Test/container.md +++ b/docs/reference/action-types/Test/container.md @@ -196,11 +196,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Test/exec.md b/docs/reference/action-types/Test/exec.md index f276b9f3ff..0a67f55e33 100644 --- a/docs/reference/action-types/Test/exec.md +++ b/docs/reference/action-types/Test/exec.md @@ -194,11 +194,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Test/hadolint.md b/docs/reference/action-types/Test/hadolint.md index 190a1530d9..678a9debed 100644 --- a/docs/reference/action-types/Test/hadolint.md +++ b/docs/reference/action-types/Test/hadolint.md @@ -200,11 +200,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Test/helm-pod.md b/docs/reference/action-types/Test/helm-pod.md index e86e11b529..2027dee7cd 100644 --- a/docs/reference/action-types/Test/helm-pod.md +++ b/docs/reference/action-types/Test/helm-pod.md @@ -196,11 +196,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Test/kubernetes-exec.md b/docs/reference/action-types/Test/kubernetes-exec.md index f41d070b22..5164fff0f4 100644 --- a/docs/reference/action-types/Test/kubernetes-exec.md +++ b/docs/reference/action-types/Test/kubernetes-exec.md @@ -196,11 +196,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/action-types/Test/kubernetes-pod.md b/docs/reference/action-types/Test/kubernetes-pod.md index ee17a139ce..90da7590fb 100644 --- a/docs/reference/action-types/Test/kubernetes-pod.md +++ b/docs/reference/action-types/Test/kubernetes-pod.md @@ -196,11 +196,11 @@ If you specify multiple paths, they are merged in the order specified, i.e. the The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-action.${environment.name}.env"` (this assumes that the corresponding varfiles exist). diff --git a/docs/reference/commands.md b/docs/reference/commands.md index 783e8fca74..29d449d47c 100644 --- a/docs/reference/commands.md +++ b/docs/reference/commands.md @@ -1572,12 +1572,12 @@ providers: # # The format of the files is determined by the configured file's extension: # - # * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys - # may contain any value type. + # may contain any value type. YAML format is used by default. + # * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # - # _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of + # _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of # nested objects and arrays._ # # To use different module-level varfiles in different environments, you can template in the environment name @@ -1848,12 +1848,12 @@ actionConfigs: # # The format of the files is determined by the configured file's extension: # - # * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may - # contain any value type. + # contain any value type. YAML format is used by default. + # * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # - # _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of + # _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of # nested objects and arrays._ # # To use different varfiles in different environments, you can template in the environment name to the varfile @@ -2064,12 +2064,12 @@ actionConfigs: # # The format of the files is determined by the configured file's extension: # - # * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may - # contain any value type. + # contain any value type. YAML format is used by default. + # * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # - # _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of + # _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of # nested objects and arrays._ # # To use different varfiles in different environments, you can template in the environment name to the varfile @@ -2219,12 +2219,12 @@ actionConfigs: # # The format of the files is determined by the configured file's extension: # - # * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may - # contain any value type. + # contain any value type. YAML format is used by default. + # * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # - # _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of + # _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of # nested objects and arrays._ # # To use different varfiles in different environments, you can template in the environment name to the varfile @@ -2374,12 +2374,12 @@ actionConfigs: # # The format of the files is determined by the configured file's extension: # - # * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may - # contain any value type. + # contain any value type. YAML format is used by default. + # * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # - # _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of + # _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of # nested objects and arrays._ # # To use different varfiles in different environments, you can template in the environment name to the varfile @@ -2524,12 +2524,12 @@ moduleConfigs: # # The format of the files is determined by the configured file's extension: # - # * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may - # contain any value type. + # contain any value type. YAML format is used by default. + # * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # - # _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of + # _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of # nested objects and arrays._ # # To use different module-level varfiles in different environments, you can template in the environment name @@ -3098,12 +3098,12 @@ modules: # # The format of the files is determined by the configured file's extension: # - # * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may - # contain any value type. + # contain any value type. YAML format is used by default. + # * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # - # _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of + # _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of # nested objects and arrays._ # # To use different module-level varfiles in different environments, you can template in the environment name diff --git a/docs/reference/config-template-config.md b/docs/reference/config-template-config.md index f82d97e21b..e87dedfe06 100644 --- a/docs/reference/config-template-config.md +++ b/docs/reference/config-template-config.md @@ -171,12 +171,12 @@ modules: # # The format of the files is determined by the configured file's extension: # - # * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may - # contain any value type. + # contain any value type. YAML format is used by default. + # * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # - # _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of + # _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of # nested objects and arrays._ # # To use different module-level varfiles in different environments, you can template in the environment name @@ -569,11 +569,11 @@ module-level `variables` field. The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different module-level varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-module.${environment.name}.env` (this assumes that the corresponding diff --git a/docs/reference/module-types/configmap.md b/docs/reference/module-types/configmap.md index 207d20ecb2..62c23ee283 100644 --- a/docs/reference/module-types/configmap.md +++ b/docs/reference/module-types/configmap.md @@ -154,12 +154,12 @@ variables: # # The format of the files is determined by the configured file's extension: # -# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may -# contain any value type. +# contain any value type. YAML format is used by default. +# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # -# _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested +# _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested # objects and arrays._ # # To use different module-level varfiles in different environments, you can template in the environment name @@ -460,11 +460,11 @@ module-level `variables` field. The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different module-level varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-module.${environment.name}.env` (this assumes that the corresponding diff --git a/docs/reference/module-types/conftest.md b/docs/reference/module-types/conftest.md index 9fed68e787..14ac9c5f64 100644 --- a/docs/reference/module-types/conftest.md +++ b/docs/reference/module-types/conftest.md @@ -157,12 +157,12 @@ variables: # # The format of the files is determined by the configured file's extension: # -# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may -# contain any value type. +# contain any value type. YAML format is used by default. +# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # -# _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested +# _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested # objects and arrays._ # # To use different module-level varfiles in different environments, you can template in the environment name @@ -468,11 +468,11 @@ module-level `variables` field. The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different module-level varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-module.${environment.name}.env` (this assumes that the corresponding diff --git a/docs/reference/module-types/container.md b/docs/reference/module-types/container.md index 85b4fbc752..e1f9eb6a40 100644 --- a/docs/reference/module-types/container.md +++ b/docs/reference/module-types/container.md @@ -169,12 +169,12 @@ variables: # # The format of the files is determined by the configured file's extension: # -# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may -# contain any value type. +# contain any value type. YAML format is used by default. +# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # -# _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested +# _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested # objects and arrays._ # # To use different module-level varfiles in different environments, you can template in the environment name @@ -1041,11 +1041,11 @@ module-level `variables` field. The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different module-level varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-module.${environment.name}.env` (this assumes that the corresponding diff --git a/docs/reference/module-types/exec.md b/docs/reference/module-types/exec.md index 0d5a3ae795..907efe5a01 100644 --- a/docs/reference/module-types/exec.md +++ b/docs/reference/module-types/exec.md @@ -166,12 +166,12 @@ variables: # # The format of the files is determined by the configured file's extension: # -# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may -# contain any value type. +# contain any value type. YAML format is used by default. +# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # -# _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested +# _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested # objects and arrays._ # # To use different module-level varfiles in different environments, you can template in the environment name @@ -650,11 +650,11 @@ module-level `variables` field. The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different module-level varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-module.${environment.name}.env` (this assumes that the corresponding diff --git a/docs/reference/module-types/hadolint.md b/docs/reference/module-types/hadolint.md index 2506ff2f61..0f2ebe73be 100644 --- a/docs/reference/module-types/hadolint.md +++ b/docs/reference/module-types/hadolint.md @@ -160,12 +160,12 @@ variables: # # The format of the files is determined by the configured file's extension: # -# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may -# contain any value type. +# contain any value type. YAML format is used by default. +# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # -# _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested +# _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested # objects and arrays._ # # To use different module-level varfiles in different environments, you can template in the environment name @@ -459,11 +459,11 @@ module-level `variables` field. The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different module-level varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-module.${environment.name}.env` (this assumes that the corresponding diff --git a/docs/reference/module-types/helm.md b/docs/reference/module-types/helm.md index 3476d5ed23..32841ef588 100644 --- a/docs/reference/module-types/helm.md +++ b/docs/reference/module-types/helm.md @@ -162,12 +162,12 @@ variables: # # The format of the files is determined by the configured file's extension: # -# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may -# contain any value type. +# contain any value type. YAML format is used by default. +# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # -# _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested +# _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested # objects and arrays._ # # To use different module-level varfiles in different environments, you can template in the environment name @@ -920,11 +920,11 @@ module-level `variables` field. The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different module-level varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-module.${environment.name}.env` (this assumes that the corresponding diff --git a/docs/reference/module-types/jib-container.md b/docs/reference/module-types/jib-container.md index f9bb981b25..209b2c544d 100644 --- a/docs/reference/module-types/jib-container.md +++ b/docs/reference/module-types/jib-container.md @@ -237,12 +237,12 @@ variables: # # The format of the files is determined by the configured file's extension: # -# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may -# contain any value type. +# contain any value type. YAML format is used by default. +# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # -# _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested +# _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested # objects and arrays._ # # To use different module-level varfiles in different environments, you can template in the environment name @@ -1256,11 +1256,11 @@ module-level `variables` field. The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different module-level varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-module.${environment.name}.env` (this assumes that the corresponding diff --git a/docs/reference/module-types/kubernetes.md b/docs/reference/module-types/kubernetes.md index f4946003d9..915c0d420e 100644 --- a/docs/reference/module-types/kubernetes.md +++ b/docs/reference/module-types/kubernetes.md @@ -161,12 +161,12 @@ variables: # # The format of the files is determined by the configured file's extension: # -# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may -# contain any value type. +# contain any value type. YAML format is used by default. +# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # -# _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested +# _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested # objects and arrays._ # # To use different module-level varfiles in different environments, you can template in the environment name @@ -903,11 +903,11 @@ module-level `variables` field. The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different module-level varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-module.${environment.name}.env` (this assumes that the corresponding diff --git a/docs/reference/module-types/persistentvolumeclaim.md b/docs/reference/module-types/persistentvolumeclaim.md index d044cafcea..1fd6cf0708 100644 --- a/docs/reference/module-types/persistentvolumeclaim.md +++ b/docs/reference/module-types/persistentvolumeclaim.md @@ -154,12 +154,12 @@ variables: # # The format of the files is determined by the configured file's extension: # -# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may -# contain any value type. +# contain any value type. YAML format is used by default. +# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # -# _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested +# _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested # objects and arrays._ # # To use different module-level varfiles in different environments, you can template in the environment name @@ -523,11 +523,11 @@ module-level `variables` field. The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different module-level varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-module.${environment.name}.env` (this assumes that the corresponding diff --git a/docs/reference/module-types/pulumi.md b/docs/reference/module-types/pulumi.md index d045282918..00baa08d55 100644 --- a/docs/reference/module-types/pulumi.md +++ b/docs/reference/module-types/pulumi.md @@ -156,12 +156,12 @@ variables: # # The format of the files is determined by the configured file's extension: # -# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may -# contain any value type. +# contain any value type. YAML format is used by default. +# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # -# _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested +# _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested # objects and arrays._ # # To use different module-level varfiles in different environments, you can template in the environment name @@ -539,11 +539,11 @@ module-level `variables` field. The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different module-level varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-module.${environment.name}.env` (this assumes that the corresponding diff --git a/docs/reference/module-types/templated.md b/docs/reference/module-types/templated.md index 88da07a6fb..5527d13de8 100644 --- a/docs/reference/module-types/templated.md +++ b/docs/reference/module-types/templated.md @@ -148,12 +148,12 @@ variables: # # The format of the files is determined by the configured file's extension: # -# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may -# contain any value type. +# contain any value type. YAML format is used by default. +# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # -# _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested +# _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested # objects and arrays._ # # To use different module-level varfiles in different environments, you can template in the environment name @@ -452,11 +452,11 @@ module-level `variables` field. The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different module-level varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-module.${environment.name}.env` (this assumes that the corresponding diff --git a/docs/reference/module-types/terraform.md b/docs/reference/module-types/terraform.md index 20ef9385dc..6099b116ff 100644 --- a/docs/reference/module-types/terraform.md +++ b/docs/reference/module-types/terraform.md @@ -162,12 +162,12 @@ variables: # # The format of the files is determined by the configured file's extension: # -# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may -# contain any value type. +# contain any value type. YAML format is used by default. +# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # -# _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested +# _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested # objects and arrays._ # # To use different module-level varfiles in different environments, you can template in the environment name @@ -489,11 +489,11 @@ module-level `variables` field. The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ To use different module-level varfiles in different environments, you can template in the environment name to the varfile name, e.g. `varfile: "my-module.${environment.name}.env` (this assumes that the corresponding diff --git a/docs/reference/project-config.md b/docs/reference/project-config.md index e408ff474f..e27d4d2eb6 100644 --- a/docs/reference/project-config.md +++ b/docs/reference/project-config.md @@ -67,12 +67,12 @@ environments: # # The format of the files is determined by the configured file's extension: # - # * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may - # contain any value type. + # contain any value type. YAML format is used by default. + # * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # - # _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of + # _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of # nested objects and arrays._ # # If you don't set the field and the `garden..env` file does not exist, @@ -192,12 +192,12 @@ sources: # # The format of the files is determined by the configured file's extension: # -# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may -# contain any value type. +# contain any value type. YAML format is used by default. +# * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). # * `.json` - JSON. Must contain a single JSON _object_ (not an array). # -# _NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested +# _NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested # objects and arrays._ # # If you don't set the field and the `garden.env` file does not exist, we simply ignore it. @@ -332,11 +332,11 @@ _environment-specific_ `variables` field. The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ If you don't set the field and the `garden..env` file does not exist, we simply ignore it. If you do override the default value and the file doesn't exist, an error will be thrown. @@ -679,11 +679,11 @@ project-wide `variables` field. The format of the files is determined by the configured file's extension: +* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. YAML format is used by default. * `.env` - Standard "dotenv" format, as defined by [dotenv](https://github.com/motdotla/dotenv#rules). -* `.yaml`/`.yml` - YAML. The file must consist of a YAML document, which must be a map (dictionary). Keys may contain any value type. * `.json` - JSON. Must contain a single JSON _object_ (not an array). -_NOTE: The default varfile format will change to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ +_NOTE: The default varfile format was changed to YAML in Garden v0.13, since YAML allows for definition of nested objects and arrays._ If you don't set the field and the `garden.env` file does not exist, we simply ignore it. If you do override the default value and the file doesn't exist, an error will be thrown.