Switch log level of terragrunt dependency fetching informational messages #1628
Conversation
This file contains 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
brikis98
previously approved these changes
Apr 2, 2021
Good point - updated to use debug: 6d40576 |
|
Thanks for review! Going to merge this in now. |
This was referenced Aug 5, 2021
This was referenced Aug 5, 2021
This was referenced Aug 5, 2021
This was referenced Aug 5, 2021
This was referenced Aug 5, 2021
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.
Related to #1625
This updates the informational messages related to dependency fetching optimizations to info log level from warning. I initially made these warning to make it more visible, but in hindsight these should have been
infolevel because they are purely informational.Warning indicates that something might be amiss and the user needs to make changes. In this case, there is probably nothing wrong here because there are many valid use cases of setting up terragrunt without
remote_stateblocks (e.g., if your project uses remote state that is not backed bys3orgcs). Thus info log level seems more appropriate for these messages.