Hey! We have been using Garden 0.12 and planning to move on for version 0.13 then 0.14. The problem we are facing atm, is that we have a base-chart, that is declared as a Module. We use it to specify common variables across our charts. The way we used it in 0.12:

yaml
kind: Module
description: Base Chart
name: base-chart
type: helm
skipDeploy: true
allowPublish: false
spec:
  values: ...
---
kind: Module
name: chalco
type: helm
base: base-chart
values: ...

(We didn't find a migration path to apply the

skipDeploy: true

field also.) Could you please give us some ideas how we can do this in version 0.13 / 0.14?

@jolly-motorcycle-47330 While we do recommend using actions, you can keep using Modules even in Garden 0.14. The base chart functionality still exists and works in Garden 0.14. If you want to accomplish re-using values when using the new action-based config, you can use the

$merge

template syntax instead:

kind: Deploy
name: base-chart
type: exec
variables:
  commonValues:
    foo: bar
    baz: false

--- 
kind: Deploy
name: ehalco
type: helm
values:
  $merge: ${actions.deploy.base-chart.vars.commonValues}
  specific:
    values: are-here