Actions
Last updated
Last updated
You need to write Garden Deploy action configs next to the pulumi stacks you'd like to include in your project. These should be located in the same directory as the stack config, or in an enclosing directory.
For example:
In case you want to use different backends for different Garden environments and you want to use deploy action specific pulumi managed state backend organizations, you can configure your deploy actions as follows. This example uses two different pulumi backends. For the prod
environment it uses the pulumi managed state backend and for the dev
environment it uses a self managed S3 backend.
Note that when you use a self managed state backend spec.cacheStatus
needs to be set to false
, since caching is only available with the pulumi managed state backend. The same applies to spec.orgName
which only makes sense in the context of the pulumi managed state backend. Please ensure that spec.orgName
is set to null
or empty string ""
for all the environments that are not using the pulumi managed state backend.
See the for more info on each available config field (and how/when to use them).