Skip to content
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

[8.x](backport #41920) x-pack/filebeat/input/httpjson: redact authorization headers in logging #41950

Merged
merged 2 commits into from
Dec 17, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Dec 8, 2024

This requires a small duplication of the mapstr.M API to workaround an issue in that type that can result in corruption of data.

Proposed commit message

x-pack/filebeat/input/httpjson: redact authentication headers in logging

This requires a small duplication of the mapstr.M API to workaround an
issue in that type that can result in corruption of data.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs


This is an automatic backport of pull request #41920 done by [Mergify](https://mergify.com).

…ng (#41920)

This requires a small duplication of the mapstr.M API to workaround an
issue in that type that can result in corruption of data.

(cherry picked from commit a641687)
@mergify mergify bot added the backport label Dec 8, 2024
@mergify mergify bot requested a review from a team as a code owner December 8, 2024 21:16
@mergify mergify bot assigned efd6 Dec 8, 2024
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Dec 8, 2024
@botelastic
Copy link

botelastic bot commented Dec 8, 2024

This pull request doesn't have a Team:<team> label.

Copy link
Contributor Author

mergify bot commented Dec 9, 2024

This pull request has not been merged yet. Could you please review and merge it @efd6? 🙏

Copy link
Contributor Author

mergify bot commented Dec 16, 2024

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/8.x/pr-41920 upstream/mergify/bp/8.x/pr-41920
git merge upstream/8.x
git push upstream mergify/bp/8.x/pr-41920

Copy link
Contributor Author

mergify bot commented Dec 16, 2024

This pull request has not been merged yet. Could you please review and merge it @efd6? 🙏

@efd6 efd6 enabled auto-merge (squash) December 17, 2024 19:44
@efd6 efd6 merged commit bb47b7f into 8.x Dec 17, 2024
19 of 22 checks passed
@efd6 efd6 deleted the mergify/bp/8.x/pr-41920 branch December 17, 2024 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants