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.

Sign up for GitHub

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

Jump to bottom

[8.7](backport #35268) [Filebeat] Fix conditions to decode_json_fields and which pipeline to run #35331

Merged
merged 1 commit into from
May 8, 2023
Merged

[8.7](backport #35268) [Filebeat] Fix conditions to decode_json_fields and which pipeline to run #35331

merged 1 commit into from
May 8, 2023

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented May 4, 2023 •
edited by zube bot
Loading

This is an automatic backport of pull request #35268 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

@crespocarlos @mergify
[Filebeat] Fix conditions to decode_json_fields and which pipeline to…
ecf5a25 
… run (#35268)

* Fix conditions to decode_json_fields and which pipeline to run

* Fix pipeline condition

* Propery merge ingest log content

(cherry picked from commit 3ee25d0)
@mergify mergify bot requested a review from a team as a code owner May 4, 2023 18:32
@mergify mergify bot added the backport label May 4, 2023
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label May 4, 2023
@botelastic
Copy link

botelastic bot commented May 4, 2023

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

  • Start Time: 2023-05-04T18:33:13.152+0000

  • Duration: 73 min 40 sec

Test stats 🧪

Test Results
Failed 0
Passed 7698
Skipped 746
Total 8444

💚 Flaky test report

Tests succeeded.

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

@mergify
Copy link
Contributor Author

mergify bot commented May 8, 2023

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

@crespocarlos crespocarlos merged commit 8ba524d into 8.7 May 8, 2023
@crespocarlos crespocarlos deleted the mergify/bp/8.7/pr-35268 branch May 8, 2023 11:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@crespocarlos crespocarlos

Labels
backport needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@elasticmachine @crespocarlos