Garden 0.12.16 is out! 🎉
This release introduces a few new features and improvements, along with several bug fixes.
See the changelog below for a full list of changes.
Finally, thanks to everyone who's been providing feedback and suggestions!
Faster build staging
The new, faster build staging system introduced in 0.12.10 as an experimental option has now been made the default.
This can dramatically speed up the build staging step for many projects.
Users who had previously opted in to the new build staging system using the GARDEN_EXPERIMENTAL_BUILD_STAGE environment variable no longer need to set that environment variable.
In turn, you can now switch back to the older rsync-based build sync system by setting GARDEN_LEGACY_BUILD_STAGE=true in your environment, in case any unexpected issues come up.
Workflows: Directly provide env vars to script steps
A map of environment variables can now be provided to individual workflow script steps. This can make scripts steps easier to write, maintain and debug.
Array concatenation in template strings
Array values can now be concatenated in template strings. For example:
kind: Project
# ...
variables:
some-values: ["a", "b"]
other-values: ["c", "d"]
---
kind: Module
type: helm
# ...
values:
some-array: ${var.some-values + var.other-values}
...See the variables and templating guide for more details on Garden's template string capabilities.
--skip option for the deploy command
This option allows skipping specific services when running garden deploy, nice and simple.
More flexible CLI options
You can now use the --name option multiple times for the garden test command, multiple --hot parameters for deploy commands etc., instead of comma-separating on the same parameter.
More pod spec fields supported in tasks and tests
For helm and kubernetes modules, we now include most pod spec fields from the service resource when running tasks and tests. This allows for more flexibility in test/task execution.
See the reference documentation for the helm and kubernetes (under tests[].resource and tasks[].resource)for a full list of pod spec fields from the service resource that are included when running a task/test for helm/kubernetes modules.
Changelog
Features
- workflows: add envVars field for script steps (857e8458)
- cli: add --skip parameter to deploy command (10bc98fa)
- k8s: use pod spec fields in tasks and tests (ce1e8ed3)
- templates: allow concatenating arrays with + operator (4b8a5bb1)
Improvements
- cli: allow multiple instances of array option parameters (844126e6)
- core: default to new build staging mechanism (5a218941)
Bug Fixes
- cli: regression in exec command parameter handling (bea46edf)
- k8s: fix potential GCR auth issue + simpler GKE+GCR instructions (6df0fa4a)
- k8s: issues with GCR auth when running in-cluster builds on GKE (1d01ed6c)
- workflows: error referencing undefined vars in workflow templates (7591cb17)
- config: pass optional templates through during partial resolution (c4dac8b8)
- k8s: error in status checks for missing CRD manifests (4713cbd2)
- k8s: fix some issues with KinD and add CI tests (78e79c13)
- k8s: fix issues with minikube v1.17 (9b6015c1)