TCP Listener: fix bug in parsing TCP listener settings for proxy_protocol_behavior
#27459
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
…nauthorized' rather than 'deny_authorized' which was incorrect
peteski22
added
bug
github-actions
bot
added
the
hashicorp-contributed-pr
|
CI Results: |
|
Build Results: |
6 tasks
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.
Description
This PR fixes a bug which prevented Vault server from starting with TCP listener configuration that attempted to set
proxy_protocol_behaviortodeny_unauthorized, which is part of the public Vault documentation.Previously the expected setting during parsing was
deny_authorizedwhich was incorrect.Docs screenshot for safety:
Resolves: #26439