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 #39006) [filebeat][websocket] - Updated Input title to align with existing inputs #39008

Merged
merged 2 commits into from
Apr 22, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 17, 2024

Type of change

Please label this PR with one of the following labels, depending on the scope of your change:

  • Docs

Proposed commit message

Updated Input title to align with existing inputs.

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

Screenshots

Logs


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

…puts (#39006)

* Updated input title to align with existing inputs

(cherry picked from commit 5bc43ff)
@mergify mergify bot added the backport label Apr 17, 2024
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 17, 2024
@elasticmachine
Copy link
Collaborator

elasticmachine commented Apr 17, 2024

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Duration: 8 min 25 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

Copy link
Contributor Author

mergify bot commented Apr 18, 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-39006 upstream/mergify/bp/8.13/pr-39006
git merge upstream/8.13
git push upstream mergify/bp/8.13/pr-39006

Copy link
Contributor Author

mergify bot commented Apr 22, 2024

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

@ShourieG ShourieG enabled auto-merge (squash) April 22, 2024 09:52
@ShourieG ShourieG added Team:Security-Service Integrations Security Service Integrations Team and removed needs_team Indicates that the issue/PR needs a Team:* label labels Apr 22, 2024
@elasticmachine
Copy link
Collaborator

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

@ShourieG ShourieG merged commit d0e0779 into 8.13 Apr 22, 2024
14 of 22 checks passed
@ShourieG ShourieG deleted the mergify/bp/8.13/pr-39006 branch April 22, 2024 10:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Team:Security-Service Integrations Security Service Integrations Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants