Garden 0.12.36 is out! 🎉

This release includes several bug fixes and improvements, and a major new feature: Dev mode for local services! This is very useful when you want to run one or more services locally with Garden during development.

Many thanks to @ohookins for his contribution to this release.

Happy hacking!

Dev mode for local (exec) services

When an exec service is deployed in dev mode, Garden assumes that the service's command starts a persistent process and does not wait for it return. The logs from the process can be retrieved via the garden logs command as usual.

If a statusCommand is set for the service, Garden will wait until it returns a zero exit code before considering the service ready. Otherwise it considers the service immediately ready.

All in all, this makes it a lot more convenient to work with locally-running services in Garden. A great use-case for this is to run one or more services locally while also deploying other services to a Kubernetes cluster. In many cases, this can lead to faster testing and debugging when rapidly iterating on services.

We will be writing a how-to guide for this functionality soon, but in the meantime, please check out the updated reference documentation for the exec module type.

Changelog

Features

• core: support persistent local processes (40c21a00)
• core: add template string sha256 function (ae49bd7b)

Improvements

• k8s: bump BuildKit version to 0.9.3 (34ef856c)

Bug Fixes

• cli: allow running garden CLI in custom Command exec field (6c8577a8)
• core: treat null/false as undefined for container image field (65e7f7f8)
• core: add missing await for user prompt (0696fb4f)
• core: fix infinite recursion that could cause OOM error (c1c6c896)
• exec: ensure we stream error log entries (08b98ca1)
• k8s: sync error with space in user home directory name (7f55c31b)
• scripts: fixed deps installation script (f902f404)