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.13](backport #38534) [DOCS] Add the read_pipeline cluster privilege to winlogbeat documentation #39490

Closed
wants to merge 4 commits into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented May 9, 2024

Add the "read_pipeline" privilege to the Grant privileges and roles needed for publishing documentation as reported in the Grant access using API keys.

Proposed commit message

[Winlogbeat][Doc] Add read_pipeline cluster privilege to winlogbeat

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.

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Adhere to the least privilege principles

Screenshots

Logs


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

…he `auto_configure` index privilege to beats documentation (#38534)

* [DOCS] Removed reference to the Stack GS (#32119)

* Update users.asciidoc

Add the "read_pipeline" privilege for Winlogbeat too

* [Docs] add auto_configure index privilege to the required permissions for beat agents

* Update link that was broken

---------

Co-authored-by: debadair <[email protected]>
Co-authored-by: Andrew Kroh <[email protected]>
(cherry picked from commit edf4568)
@mergify mergify bot requested a review from a team as a code owner May 9, 2024 14:49
@mergify mergify bot added the backport label May 9, 2024
@mergify mergify bot requested review from AndersonQ and belimawr and removed request for a team May 9, 2024 14:49
@mergify mergify bot assigned herrBez May 9, 2024
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label May 9, 2024
@botelastic
Copy link

botelastic bot commented May 9, 2024

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

Copy link
Contributor Author

mergify bot commented May 13, 2024

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

Copy link
Contributor Author

mergify bot commented May 15, 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.13/pr-38534 upstream/mergify/bp/8.13/pr-38534
git merge upstream/8.13
git push upstream mergify/bp/8.13/pr-38534

Copy link
Contributor Author

mergify bot commented May 20, 2024

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

Copy link
Contributor Author

mergify bot commented May 27, 2024

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

1 similar comment
Copy link
Contributor Author

mergify bot commented Jun 3, 2024

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

Copy link
Contributor Author

mergify bot commented Jun 10, 2024

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

@AndersonQ AndersonQ removed their request for review June 12, 2024 07:08
Copy link
Contributor Author

mergify bot commented Jun 17, 2024

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

2 similar comments
Copy link
Contributor Author

mergify bot commented Jun 24, 2024

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

Copy link
Contributor Author

mergify bot commented Jul 1, 2024

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

@pierrehilbert
Copy link
Collaborator

pierrehilbert commented Jul 1, 2024

@herrBez would you mind to take care of this backport please? We are not planning to build new 8.13 so probably good to be closed.

@herrBez
Copy link
Contributor

herrBez commented Jul 1, 2024

Hi, thank you. I agree we can close this. The one for version 8.14 have been fixed. So let's close this. Thank you for your patience.

@herrBez herrBez closed this Jul 1, 2024
@mergify mergify bot deleted the mergify/bp/8.13/pr-38534 branch July 1, 2024 12:52
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.

3 participants