You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A change in a terraform stack which is applied by garden as part of the provider initialization via initRoot does not invalidate the provider status cache. This means that unless using --force-refresh the terraform stack is never updated.
Expected behavior
The stack deployed as initRoot should when changed cause a cache miss.
Garden Bonsai (0.13) Bug
Current Behavior
A change in a terraform stack which is applied by garden as part of the provider initialization via
initRoot
does not invalidate the provider status cache. This means that unless using--force-refresh
the terraform stack is never updated.Expected behavior
The stack deployed as
initRoot
should when changed cause a cache miss.Reproducible example
garden.yaml:
terraform/main.tf
The above terraform config changes the bucket name on each apply.
Workaround
Using
--force-refresh
causes a provider re-initialization and therefore the change is detected.Suggested solution(s)
The stack deployed as
initRoot
should when changed cause a cache miss.Additional context
Your environment
garden version
0.13.30The text was updated successfully, but these errors were encountered: