We use Terragrunt and noticed that Spacelift runs 2 plans during tracked runs for Terragrunt, which for a merge-before-apply workflow means we’re now up to 3 plans for a single change to be applied. The impact of this is low for a directory with a short plan time, but could be major for directories where a plan takes a longer time.
Support mentioned that the reason for this is because of Terragrunt’s mocked_outputs features and not wanting to risk faked values being used to create infrastructure. However, we do not use mocked_outputs at all in our Terragrunt. Would it be possible to let us opt-in to skip the extra plan phase and save some time during our apply phases since we understand the risks but also feel they don’t apply to our use case?
Please authenticate to join the conversation.
🔭 Discovery
💡 Feature Requests
Terragrunt
4 months ago
Get notified by email when there are changes.
🔭 Discovery
💡 Feature Requests
Terragrunt
4 months ago
Get notified by email when there are changes.