Deprecations and major-version updates

Deprecations and major-version updates

The next major version of Garden, 0.14, will contain breaking changes. To make the update as seamless as possible for your team, avoid functionality that has been deprecated in Garden 0.13.

When using apiVersion: garden.io/v1 in your project configuration file, Garden will warn you if your configuration depends on features that will be removed in Garden 0.14.

EXPERIMENTAL: You can opt-in to the new behaviour in Garden 0.14 by using apiVersion: garden.io/v2. This setting will make Garden throw errors whenever it detects usage of deprecated functionality.

Please note that as of today, not all warnings are in place, so we are still working on the list of breaking changes. Once the list of breaking changes is final, we will make this known here.

Breaking changes

Kubernetes provider configuration

The `deploymentStrategy` config field

Do not use this config field. It has no effect as the experimental support for blue/green deployments (via the blue-green strategy) has been removed.

Project configuration

The `dotIgnoreFiles` config field

Use the dotIgnoreFile field instead. It only allows specifying one filename.

For more information, please refer to the dotIgnoreFile reference documentation.

Using `apiVersion: garden.io/v0` in the project config

Use apiVersion: garden.io/v1 or higher instead.

For more information, please refer to the apiVersion reference documentation.

The `modules` config field

Please use the scan field instead.

For more information, please refer to the scan reference documentation.

Garden Commands

The Kubernetes plugin command `cluster-init`

Do not use this command. It has no effect.