As of today, we’re putting Garden Bonsai (0.13) into beta!

Most of our docs haven’t been updated yet (we’ll be working on that in the coming days and weeks), but here’s a guide for migrating to Bonsai: https://docs.garden.io/v/bonsai-release/tutorials/migrating-to-bonsai

We also recommend having a look at the updated example projects for examples of action configs: https://github.com/garden-io/garden/tree/0.13/examples

Note for Garden Cloud users: We’re still making the needed changes to Cloud’s API to support Garden Bonsai, so you won’t have access to the full functionality of Cloud until those have been rolled out (which should be done in the next week or so).

Here are some of the highlights:

• Actions instead of modules: A new, more lightweight, more flexible and more powerful way to define your Stack Graph.
• Modules are now converted into actions internally, so this is backwards-compatible with 0.12.
• Any action can depend on any action: This means that e.g. Tests can depend on Builds.
• The new kubernetes-exec Run and Test action types introduce rebuild-free Tests and Runs.
  • This is great when running your tests while coding. Want to run your integ/e2e tests lightning fast without rebuilding? This is your jam.
• For Runs (known as tasks in 0.12), you can now also shave off a significant amount of time when spinning up your stack.
  • Example: If you need to run a script against your database after it’s deployed before it’s ready (e.g. to init a schema or load test data), you no longer need to spin up a one-off pod to do this.
    • Simply exec the command in the running service by adding a dependency on a kubernetes-exec Run that executes the script.
  • Also useful for simple scripts you want to run in your services (e.g. for generating DB migrations or refreshing your dev DB).
• Greatly improved logging, with more detail shown by default.
• An interactive dev command! garden dev now starts an interactive session where you can...
  • Start and stop code syncing for individual deployments with or without redeploying.
  • Run individual actions, e.g. Tests or Runs (a perfect combo with the new kubernetes-exec actions).
• Basically interactively access the whole Garden CLI without having to re-scan your project or init providers, making for a much snappier developer experience in total.

There’s more exciting stuff coming up in the following days and weeks, so stay tuned!

We’d love to hear your feedback and bug reports, so we can move to a general-availability release as soon as possible.