-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: known issue for listener using proxy_protocol _behavior
#27628
Conversation
CI Results: |
Build Results: |
…shicorp/vault into peteski22/VAULT-6803/docs/known-issue
website/content/partials/known-issues/config_listener_proxy_protocol_behavior_issue.mdx
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! Great detail -- and sorry for the confusion on the versions.
website/content/partials/known-issues/config_listener_proxy_protocol_behavior_issue.mdx
Outdated
Show resolved
Hide resolved
website/content/partials/known-issues/config_listener_proxy_protocol_behavior_issue.mdx
Outdated
Show resolved
Hide resolved
website/content/partials/known-issues/config_listener_proxy_protocol_behavior_issue.mdx
Outdated
Show resolved
Hide resolved
website/content/partials/known-issues/config_listener_proxy_protocol_behavior_issue.mdx
Outdated
Show resolved
Hide resolved
website/content/partials/known-issues/config_listener_proxy_protocol_behavior_issue.mdx
Outdated
Show resolved
Hide resolved
…otocol_behavior_issue.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
website/content/partials/known-issues/config_listener_proxy_protocol_behavior_issue.mdx
Outdated
Show resolved
Hide resolved
website/content/partials/known-issues/config_listener_proxy_protocol_behavior_issue.mdx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving to unblock publication. Please be sure to apply the suggestions before merging.
…otocol_behavior_issue.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
…otocol_behavior_issue.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
* docs: known issue for listener proxy protocol behavior * relative links * update text * Update website/content/partials/known-issues/config_listener_proxy_protocol_behavior_issue.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> * change one of the uses of 'this' * Update website/content/partials/known-issues/config_listener_proxy_protocol_behavior_issue.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> * Update website/content/partials/known-issues/config_listener_proxy_protocol_behavior_issue.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> --------- Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
…) (#27665) * docs: known issue for listener proxy protocol behavior --------- Co-authored-by: Peter Wilson <peter.wilson@hashicorp.com> Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
Description
Documents a known issue which impacts various versions of Vault.
TODO only if you're a HashiCorp employee
getting backported to N-2, use the new style
backport/ent/x.x.x+ent
labelsinstead of the old style
backport/x.x.x
labels.the normal
backport/x.x.x
label (there should be only 1).of a public function, even if that change is in a CE file, double check that
applying the patch for this PR to the ENT repo and running tests doesn't
break any tests. Sometimes ENT only tests rely on public functions in CE
files.
in the PR description, commit message, or branch name.
RFC: If this change has an associated RFC, please link it in the description.ENT PR: If this change has an associated ENT PR, please link it in thedescription. Also, make sure the changelog is in this PR, not in your ENT PR.