Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[8.0](backport #29751) #29747: Fix Add Network Direction processor #30125

Closed
wants to merge 1 commit into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Feb 1, 2022

This is an automatic backport of pull request #29751 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

Fix Add Network Direction processor field with dot in name.

Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
(cherry picked from commit 56b227d)
@mergify mergify bot added the backport label Feb 1, 2022
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Feb 1, 2022
@botelastic
Copy link

botelastic bot commented Feb 1, 2022

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

@elasticmachine
Copy link
Collaborator

💚 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

  • Reason: null

  • Start Time: 2022-02-01T02:47:20.243+0000

  • Duration: 142 min 32 sec

  • Commit: a00bdeb

Test stats 🧪

Test Results
Failed 0
Passed 47604
Skipped 4292
Total 51896

💚 Flaky test report

Tests succeeded.

🤖 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!)

@mergify
Copy link
Contributor Author

mergify bot commented Feb 23, 2022

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.0/pr-29751 upstream/mergify/bp/8.0/pr-29751
git merge upstream/8.0
git push upstream mergify/bp/8.0/pr-29751

@jsoriano
Copy link
Member

@legoguy1000 @andrewkroh could you please take a look to this backport?

@andrewkroh andrewkroh closed this Mar 15, 2022
@mergify mergify bot deleted the mergify/bp/8.0/pr-29751 branch March 15, 2022 18:01
# for free to join this conversation on GitHub. Already have an account? # 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.

4 participants