${runtime.services.[service-name].outputs})
key).garden deploy
in your project—just like any other Garden service!pulumi-module-a
's pulumi program uses a stack references to an IP address that's an output of pulumi-module-b
's pulumi program, you can add a dependency on pulumi-module-b
by referencing that output:pulumi-module-b
before pulumi-module-a
when running e.g. garden deploy
.stackReferences
field, you can safely set cacheStatus: true
for your module, since Garden will factor the stack output values into its version calculations.cacheStatus
is set to false
, Garden runs pulumi up
on every deploy. While this is safe and easy to reason about, it's much slower and more resource-intensive than using cacheStatus = true
.pulumi up
is a much more expensive operation (in terms of CPU, RAM and time used) than the calls to pulumi stack tag set/get
that Garden uses when cacheStatus = true
.cacheStatus = true
in your pulumi modules whenever possible, once you've made sure you've included all relevant stack references in your pulumi module configs.preview
cancel
refresh
destroy
reimport
Each of the above wraps the pulumi command with the same name, except for reimport
(which wraps pulumi export | pulumi import
—a workflow that's occasionally needed).