diff --git a/core/src/config/module.ts b/core/src/config/module.ts index 6496ca31c3..1d3a69e1e0 100644 --- a/core/src/config/module.ts +++ b/core/src/config/module.ts @@ -214,7 +214,7 @@ export const baseModuleSpecKeys = memoize(() => ({ dedent` Set this to \`true\` to disable the module. You can use this with conditional template strings to disable modules based on, for example, the current environment or other variables (e.g. \`disabled: \${environment.name == "prod"}\`). This can be handy when you only need certain modules for specific environments, e.g. only for development. - Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which case building this module is necessary for the dependant to be built). + Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will automatically ignore those dependency declarations. Note however that template strings referencing the module's service or task outputs (i.e. runtime outputs) will fail to resolve when the module is disabled, so you need to make sure to provide alternate values for those if you're using them, using conditional expressions. ` diff --git a/docs/reference/commands.md b/docs/reference/commands.md index 29d449d47c..ca974a9824 100644 --- a/docs/reference/commands.md +++ b/docs/reference/commands.md @@ -1513,9 +1513,8 @@ providers: # ${environment.name == "prod"}`). This can be handy when you only need certain modules for specific # environments, e.g. only for development. # - # Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It - # also means that the module is not built _unless_ it is declared as a build dependency by another enabled - # module (in which case building this module is necessary for the dependant to be built). + # Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or + # run. # # If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden # will automatically ignore those dependency declarations. Note however that template strings referencing the @@ -2466,9 +2465,7 @@ moduleConfigs: # "prod"}`). This can be handy when you only need certain modules for specific environments, e.g. only for # development. # - # Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also - # means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in - # which case building this module is necessary for the dependant to be built). + # Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. # # If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden # will automatically ignore those dependency declarations. Note however that template strings referencing the @@ -3040,9 +3037,7 @@ modules: # "prod"}`). This can be handy when you only need certain modules for specific environments, e.g. only for # development. # - # Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also - # means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in - # which case building this module is necessary for the dependant to be built). + # Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. # # If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden # will automatically ignore those dependency declarations. Note however that template strings referencing the diff --git a/docs/reference/config-template-config.md b/docs/reference/config-template-config.md index e87dedfe06..af58b6b96b 100644 --- a/docs/reference/config-template-config.md +++ b/docs/reference/config-template-config.md @@ -90,9 +90,7 @@ modules: # "prod"}`). This can be handy when you only need certain modules for specific environments, e.g. only for # development. # - # Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also - # means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in - # which case building this module is necessary for the dependant to be built). + # Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. # # If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden # will automatically ignore those dependency declarations. Note however that template strings referencing the @@ -414,7 +412,7 @@ A description of the module. Set this to `true` to disable the module. You can use this with conditional template strings to disable modules based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). This can be handy when you only need certain modules for specific environments, e.g. only for development. -Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which case building this module is necessary for the dependant to be built). +Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will automatically ignore those dependency declarations. Note however that template strings referencing the module's service or task outputs (i.e. runtime outputs) will fail to resolve when the module is disabled, so you need to make sure to provide alternate values for those if you're using them, using conditional expressions. diff --git a/docs/reference/module-types/configmap.md b/docs/reference/module-types/configmap.md index 62c23ee283..b9a99cf4a8 100644 --- a/docs/reference/module-types/configmap.md +++ b/docs/reference/module-types/configmap.md @@ -74,9 +74,7 @@ description: # based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). # This can be handy when you only need certain modules for specific environments, e.g. only for development. # -# Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also -# means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which -# case building this module is necessary for the dependant to be built). +# Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. # # If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will # automatically ignore those dependency declarations. Note however that template strings referencing the module's @@ -322,7 +320,7 @@ A description of the module. Set this to `true` to disable the module. You can use this with conditional template strings to disable modules based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). This can be handy when you only need certain modules for specific environments, e.g. only for development. -Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which case building this module is necessary for the dependant to be built). +Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will automatically ignore those dependency declarations. Note however that template strings referencing the module's service or task outputs (i.e. runtime outputs) will fail to resolve when the module is disabled, so you need to make sure to provide alternate values for those if you're using them, using conditional expressions. diff --git a/docs/reference/module-types/conftest.md b/docs/reference/module-types/conftest.md index 14ac9c5f64..4ca30666fc 100644 --- a/docs/reference/module-types/conftest.md +++ b/docs/reference/module-types/conftest.md @@ -77,9 +77,7 @@ description: # based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). # This can be handy when you only need certain modules for specific environments, e.g. only for development. # -# Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also -# means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which -# case building this module is necessary for the dependant to be built). +# Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. # # If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will # automatically ignore those dependency declarations. Note however that template strings referencing the module's @@ -330,7 +328,7 @@ A description of the module. Set this to `true` to disable the module. You can use this with conditional template strings to disable modules based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). This can be handy when you only need certain modules for specific environments, e.g. only for development. -Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which case building this module is necessary for the dependant to be built). +Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will automatically ignore those dependency declarations. Note however that template strings referencing the module's service or task outputs (i.e. runtime outputs) will fail to resolve when the module is disabled, so you need to make sure to provide alternate values for those if you're using them, using conditional expressions. diff --git a/docs/reference/module-types/container.md b/docs/reference/module-types/container.md index d0cbd32861..e5c4bac869 100644 --- a/docs/reference/module-types/container.md +++ b/docs/reference/module-types/container.md @@ -82,9 +82,7 @@ description: # based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). # This can be handy when you only need certain modules for specific environments, e.g. only for development. # -# Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also -# means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which -# case building this module is necessary for the dependant to be built). +# Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. # # If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will # automatically ignore those dependency declarations. Note however that template strings referencing the module's @@ -907,7 +905,7 @@ A description of the module. Set this to `true` to disable the module. You can use this with conditional template strings to disable modules based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). This can be handy when you only need certain modules for specific environments, e.g. only for development. -Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which case building this module is necessary for the dependant to be built). +Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will automatically ignore those dependency declarations. Note however that template strings referencing the module's service or task outputs (i.e. runtime outputs) will fail to resolve when the module is disabled, so you need to make sure to provide alternate values for those if you're using them, using conditional expressions. diff --git a/docs/reference/module-types/exec.md b/docs/reference/module-types/exec.md index 907efe5a01..e8f86482fd 100644 --- a/docs/reference/module-types/exec.md +++ b/docs/reference/module-types/exec.md @@ -86,9 +86,7 @@ description: # based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). # This can be handy when you only need certain modules for specific environments, e.g. only for development. # -# Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also -# means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which -# case building this module is necessary for the dependant to be built). +# Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. # # If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will # automatically ignore those dependency declarations. Note however that template strings referencing the module's @@ -512,7 +510,7 @@ A description of the module. Set this to `true` to disable the module. You can use this with conditional template strings to disable modules based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). This can be handy when you only need certain modules for specific environments, e.g. only for development. -Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which case building this module is necessary for the dependant to be built). +Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will automatically ignore those dependency declarations. Note however that template strings referencing the module's service or task outputs (i.e. runtime outputs) will fail to resolve when the module is disabled, so you need to make sure to provide alternate values for those if you're using them, using conditional expressions. diff --git a/docs/reference/module-types/hadolint.md b/docs/reference/module-types/hadolint.md index 0f2ebe73be..825eed5393 100644 --- a/docs/reference/module-types/hadolint.md +++ b/docs/reference/module-types/hadolint.md @@ -80,9 +80,7 @@ description: # based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). # This can be handy when you only need certain modules for specific environments, e.g. only for development. # -# Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also -# means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which -# case building this module is necessary for the dependant to be built). +# Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. # # If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will # automatically ignore those dependency declarations. Note however that template strings referencing the module's @@ -321,7 +319,7 @@ A description of the module. Set this to `true` to disable the module. You can use this with conditional template strings to disable modules based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). This can be handy when you only need certain modules for specific environments, e.g. only for development. -Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which case building this module is necessary for the dependant to be built). +Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will automatically ignore those dependency declarations. Note however that template strings referencing the module's service or task outputs (i.e. runtime outputs) will fail to resolve when the module is disabled, so you need to make sure to provide alternate values for those if you're using them, using conditional expressions. diff --git a/docs/reference/module-types/helm.md b/docs/reference/module-types/helm.md index 46599142ea..64889fe3e2 100644 --- a/docs/reference/module-types/helm.md +++ b/docs/reference/module-types/helm.md @@ -76,9 +76,7 @@ description: # based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). # This can be handy when you only need certain modules for specific environments, e.g. only for development. # -# Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also -# means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which -# case building this module is necessary for the dependant to be built). +# Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. # # If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will # automatically ignore those dependency declarations. Note however that template strings referencing the module's @@ -784,7 +782,7 @@ A description of the module. Set this to `true` to disable the module. You can use this with conditional template strings to disable modules based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). This can be handy when you only need certain modules for specific environments, e.g. only for development. -Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which case building this module is necessary for the dependant to be built). +Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will automatically ignore those dependency declarations. Note however that template strings referencing the module's service or task outputs (i.e. runtime outputs) will fail to resolve when the module is disabled, so you need to make sure to provide alternate values for those if you're using them, using conditional expressions. diff --git a/docs/reference/module-types/jib-container.md b/docs/reference/module-types/jib-container.md index 16eeb2e01c..4c94527a57 100644 --- a/docs/reference/module-types/jib-container.md +++ b/docs/reference/module-types/jib-container.md @@ -150,9 +150,7 @@ description: # based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). # This can be handy when you only need certain modules for specific environments, e.g. only for development. # -# Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also -# means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which -# case building this module is necessary for the dependant to be built). +# Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. # # If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will # automatically ignore those dependency declarations. Note however that template strings referencing the module's @@ -1122,7 +1120,7 @@ A description of the module. Set this to `true` to disable the module. You can use this with conditional template strings to disable modules based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). This can be handy when you only need certain modules for specific environments, e.g. only for development. -Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which case building this module is necessary for the dependant to be built). +Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will automatically ignore those dependency declarations. Note however that template strings referencing the module's service or task outputs (i.e. runtime outputs) will fail to resolve when the module is disabled, so you need to make sure to provide alternate values for those if you're using them, using conditional expressions. diff --git a/docs/reference/module-types/kubernetes.md b/docs/reference/module-types/kubernetes.md index 0076f29a0e..000358527a 100644 --- a/docs/reference/module-types/kubernetes.md +++ b/docs/reference/module-types/kubernetes.md @@ -78,9 +78,7 @@ description: # based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). # This can be handy when you only need certain modules for specific environments, e.g. only for development. # -# Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also -# means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which -# case building this module is necessary for the dependant to be built). +# Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. # # If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will # automatically ignore those dependency declarations. Note however that template strings referencing the module's @@ -768,7 +766,7 @@ A description of the module. Set this to `true` to disable the module. You can use this with conditional template strings to disable modules based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). This can be handy when you only need certain modules for specific environments, e.g. only for development. -Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which case building this module is necessary for the dependant to be built). +Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will automatically ignore those dependency declarations. Note however that template strings referencing the module's service or task outputs (i.e. runtime outputs) will fail to resolve when the module is disabled, so you need to make sure to provide alternate values for those if you're using them, using conditional expressions. diff --git a/docs/reference/module-types/persistentvolumeclaim.md b/docs/reference/module-types/persistentvolumeclaim.md index 1fd6cf0708..7d5b600467 100644 --- a/docs/reference/module-types/persistentvolumeclaim.md +++ b/docs/reference/module-types/persistentvolumeclaim.md @@ -74,9 +74,7 @@ description: # based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). # This can be handy when you only need certain modules for specific environments, e.g. only for development. # -# Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also -# means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which -# case building this module is necessary for the dependant to be built). +# Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. # # If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will # automatically ignore those dependency declarations. Note however that template strings referencing the module's @@ -385,7 +383,7 @@ A description of the module. Set this to `true` to disable the module. You can use this with conditional template strings to disable modules based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). This can be handy when you only need certain modules for specific environments, e.g. only for development. -Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which case building this module is necessary for the dependant to be built). +Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will automatically ignore those dependency declarations. Note however that template strings referencing the module's service or task outputs (i.e. runtime outputs) will fail to resolve when the module is disabled, so you need to make sure to provide alternate values for those if you're using them, using conditional expressions. diff --git a/docs/reference/module-types/pulumi.md b/docs/reference/module-types/pulumi.md index dfdb4425e1..4460924b73 100644 --- a/docs/reference/module-types/pulumi.md +++ b/docs/reference/module-types/pulumi.md @@ -76,9 +76,7 @@ description: # based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). # This can be handy when you only need certain modules for specific environments, e.g. only for development. # -# Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also -# means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which -# case building this module is necessary for the dependant to be built). +# Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. # # If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will # automatically ignore those dependency declarations. Note however that template strings referencing the module's @@ -407,7 +405,7 @@ A description of the module. Set this to `true` to disable the module. You can use this with conditional template strings to disable modules based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). This can be handy when you only need certain modules for specific environments, e.g. only for development. -Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which case building this module is necessary for the dependant to be built). +Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will automatically ignore those dependency declarations. Note however that template strings referencing the module's service or task outputs (i.e. runtime outputs) will fail to resolve when the module is disabled, so you need to make sure to provide alternate values for those if you're using them, using conditional expressions. diff --git a/docs/reference/module-types/terraform.md b/docs/reference/module-types/terraform.md index 6099b116ff..b9b087bbfd 100644 --- a/docs/reference/module-types/terraform.md +++ b/docs/reference/module-types/terraform.md @@ -80,9 +80,7 @@ description: # based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). # This can be handy when you only need certain modules for specific environments, e.g. only for development. # -# Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also -# means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which -# case building this module is necessary for the dependant to be built). +# Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. # # If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will # automatically ignore those dependency declarations. Note however that template strings referencing the module's @@ -347,7 +345,7 @@ A description of the module. Set this to `true` to disable the module. You can use this with conditional template strings to disable modules based on, for example, the current environment or other variables (e.g. `disabled: ${environment.name == "prod"}`). This can be handy when you only need certain modules for specific environments, e.g. only for development. -Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which case building this module is necessary for the dependant to be built). +Disabling a module means that any services, tasks and tests contained in it will not be build, deployed or run. If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will automatically ignore those dependency declarations. Note however that template strings referencing the module's service or task outputs (i.e. runtime outputs) will fail to resolve when the module is disabled, so you need to make sure to provide alternate values for those if you're using them, using conditional expressions.