WIP - fix(init): do not require re-init after explicit init on clean directory #2949
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.
Description
Running
terragrunt plan --terragrunt-no-auto-init
on clean directory just afterterragrunt init
, raises confusing warning that init is needed.On 1st clean init
previousVersion
is always empty, therefore no need to mark it as init required again and this warning is misleading.How-to reproduce:
$ rm -rf .terragrunt-cache/ $ terragrunt init INFO[0000] Downloading Terraform configurations from ... Initializing the backend... ... Terraform has been successfully initialized! ... $ terragrunt plan --terragrunt-no-auto-init WARN[0000] Detected that init is needed, but Auto-Init is disabled. Continuing with further actions, but subsequent terraform commands may fail. prefix=[/path/to/stack] ...
Workaround:
TODOs
Read the Gruntwork contribution guidelines.
Release Notes (draft)
Added / Removed / Updated [X].
Removed warning when using
no-auto-init
flag after explicitinit
on clean directory.