Hello,
Would anyone know how to skip dependency resolution at terraspace
runtime ?
i.e. I have stack(s) explicitly dependent on other stack(s) via depends_on-helper. While mandatory for the initial terraspace up
, it gets in the way of reducing execution times for subsequent runs. So I am hoping a command line option could be passed to skip dependencies resolution on demand.
Example:
- velero depends on prometheus-stack
- which depends on aws-ebs-csi-driver
- which depends on external-snapshotter
- which depends on kube-base
The order must be respected on initial terraspace up
, or some stack will fail due to missing resources provided by parent stack(s).
terraspace up velero
Will run:
terraspace up kube-base # batch 1
terraspace up external-snapshotter # batch 2
terraspace up aws-ebs-csi-driver # batch 3
terraspace up prometheus-stack # batch 4
terraspace up velero # batch 5
But on subsequent runs, it would save precious time to be able to skip the runs on parent stacks. Something like:
terraspace up velero --skip-dependencies
Will run:
terraspace up velero # batch 1
I did not find an answer in the docs, apart from the following:
Terraspace always evaluates all layered tfvars files at terraspace compile time. This means helpers like
output
anddepends_on
will always register the dependencies with Terraspace if they are called.
Source: Dependencies Tfvars Considerations - Terraspace
leading me to think this might not be doable