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

filebeat/beater: improve StateStore godoc #42648

Merged
merged 1 commit into from
Feb 10, 2025
Merged

Conversation

efd6
Copy link
Contributor

@efd6 efd6 commented Feb 9, 2025

Proposed commit message

See title.

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

@efd6 efd6 added enhancement docs Team:Elastic-Agent Label for the Agent team Team:Security-Service Integrations Security Service Integrations Team labels Feb 9, 2025
@efd6 efd6 self-assigned this Feb 9, 2025
@efd6 efd6 requested a review from a team as a code owner February 9, 2025 22:24
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

@elasticmachine
Copy link
Collaborator

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@efd6 efd6 requested review from belimawr and leehinman February 9, 2025 22:24
@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Feb 9, 2025
Copy link
Contributor

mergify bot commented Feb 9, 2025

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @efd6? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

@efd6 efd6 added the backport-8.x Automated backport to the 8.x branch with mergify label Feb 9, 2025
@efd6 efd6 merged commit e642ddd into elastic:main Feb 10, 2025
31 checks passed
mergify bot pushed a commit that referenced this pull request Feb 10, 2025
efd6 added a commit that referenced this pull request Feb 10, 2025
(cherry picked from commit e642ddd)

Co-authored-by: Dan Kortschak <dan.kortschak@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.x Automated backport to the 8.x branch with mergify docs enhancement Team:Elastic-Agent Label for the Agent team Team:Security-Service Integrations Security Service Integrations Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants