feat: add fine-grained pre/post commands to terragrunt workflows#56
Merged
chris11-taylor-nttd merged 1 commit intomainfrom Feb 6, 2026
Merged
feat: add fine-grained pre/post commands to terragrunt workflows#56chris11-taylor-nttd merged 1 commit intomainfrom
chris11-taylor-nttd merged 1 commit intomainfrom
Conversation
ben-vaughan-nttd
approved these changes
Jan 29, 2026
bryce-lynn-nttd
approved these changes
Feb 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds support for arbitrary commands to be run before and after all Terragrunt plan/deploy/destroy steps. Additionally, for workflows that contain multiple steps (e.g. plan and then deploy), adds a "shared" commands structure that will apply to both for convenience.
This opens the door for repo-specific commands to be run around the core Terragrunt workflows. One immediate need is around an internal tool utilizing our Azure web_app module, which has a lifecycle rule that prevents changes to app_settings. This is done because there are other services and features within Azure that will dynamically update these configuration items, which Terraform detects as drift and then attempts to correct on next run. For setups utilizing this module, an external script to additively apply expected configurations, rather than a full sync, can be used to ensure that configurations are published through the pipeline.
Also contains a few minor formatting/indentation changes. Evidently I didn't have format-on-save turned on the last time I messed with these files.