Add config debug #444
Merged
Add config debug #444
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
denyeart
force-pushed
the
config_debug
branch
from
7f3883e to
c0017ae
Compare
bestbeforetoday
previously approved these changes
Feb 7, 2025
denyeart
force-pushed
the
config_debug
branch
2 times, most recently
from
1eb37eb to
13491f0
Compare
bestbeforetoday
previously approved these changes
Feb 7, 2025
denyeart
force-pushed
the
config_debug
branch
5 times, most recently
from
e32015b to
b34ec62
Compare
- Info log CA config upon startup (consistent with fabric peer approach) - Info log FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3 setting - Debug log when falling back to COMPATIBILITY_MODE_V1_3 authentication header validation Signed-off-by: David Enyeart <enyeart@us.ibm.com>
denyeart
force-pushed
the
config_debug
branch
from
b34ec62 to
9d4553f
Compare
bestbeforetoday
approved these changes
Feb 7, 2025
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.
Changing V1_3 compatibility mode in #435 has caused some user confusion, some additional debug logging will help:
Also take this opportunity to log the entire config upon startup to be consistent with core Fabric: