Environment resolution debug statements #607
Merged
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
Enable verbose logging when `DEBUG=gasket:*` is set to explain environment config assignment.
dbelcher-godaddy
approved these changes
Jul 12, 2023
agerard-godaddy
approved these changes
Jul 12, 2023
mmason2-godaddy
approved these changes
Jul 12, 2023
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.
Summary
A frequent category of gasket support issues relates to figuring out why gasket is not using the config settings for the expected environment. This enables using the
DEBUGenvironment variable to see various environment/config startup logging to explain what goes on when it comes to resolving configuration.Changelog
DEBUG=gasket:*is set to explain environment config assignment.Test Plan
Regression testing, making sure existing unit tests still pass