feat(terragrunt): Separate terragrunt and terraform arguments #1581
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.
Summary
This PR refactors the terragrunt module to explicitly separate terragrunt-specific arguments from terraform command arguments, improving API clarity and usability.
Motivation
The previous implementation used a single
ExtraArgs
field for all arguments, making it unclear which arguments were for terragrunt vs terraform. The--
separator logic was also handled inconsistently across different commands.Changes
ExtraArgs
field with:TerragruntArgs
: For terragrunt-specific flags (e.g.,--no-color
,--terragrunt-log-level
)TerraformArgs
: For terraform commands passed after--
separator (e.g.,plan
,apply
,-upgrade
)--
separator is now automatically added whenTerraformArgs
are presentBenefits
--
separator reduces boilerplateTesting
All existing tests have been updated and are passing:
Breaking Changes
This is a breaking change for the beta terragrunt module. Users will need to update their code to use
TerragruntArgs
andTerraformArgs
instead ofExtraArgs
.Migration Example
Before:
After: