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
I understand that unit.source of terragrunt.stack.hcl doesn't support source-maps, but the terraform.source of terragrunt.hcl does support the source-map. However, when running terragrunt stack apply, the source-map is not used for terraform.source in terragrunt.hcl . Is this also as designed?
Alternatively, if I apply the stack with terragrunt stack generate followed by terragrunt run-all apply, the source-map is respected.
I've been trying out stacks, and even though I've configured my unit.source to point to a local directory, I'd like to be able to substitute the module's source on the fly.
I understand that
unit.source
ofterragrunt.stack.hcl
doesn't support source-maps, but theterraform.source
ofterragrunt.hcl
does support the source-map. However, when runningterragrunt stack apply
, the source-map is not used forterraform.source
interragrunt.hcl
. Is this also as designed?Alternatively, if I apply the stack with
terragrunt stack generate
followed byterragrunt run-all apply
, the source-map is respected.I've been trying out stacks, and even though I've configured my
unit.source
to point to a local directory, I'd like to be able to substitute the module's source on the fly.Originally posted by @mhulscher in #3313 (comment)
The text was updated successfully, but these errors were encountered: