Preserve bare gRPC logging flag compatibility - #91
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Preserve the previous bare --log-grpc flag as payload logging while allowing --log-grpc=off|metadata|payload. Keep the previous boolean spellings and the default of no logging.
Use Kong's boolean-style custom mapper so a bare flag cannot consume the following database argument. Explicit values use "=". Update help and README.
Validation: full Go 1.25.13 emulator suite, build, and lint passed. Parser tests cover omitted and bare flags, a database named metadata, each mode, legacy boolean values, and invalid/empty values.