Skip to content

[7.17](backport #34478) [Azure Logs] Replace foreach+set combo with a script processor#34502

Merged
zmoog merged 2 commits into7.17from
mergify/bp/7.17/pr-34478
Feb 8, 2023
Merged

[7.17](backport #34478) [Azure Logs] Replace foreach+set combo with a script processor#34502
zmoog merged 2 commits into7.17from
mergify/bp/7.17/pr-34478

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Feb 7, 2023

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

* Replace foreach+set combo with a script processor

The `set` processor expands the dots contained in the field name into
subfield.

Sometimes attributes contained in `authentication_processing_details`
have dots, for example:

    # source
    {"key": "a.b.c", "value": true}

In such cases, the `set` processor would turn it into:

    # this is a side-effect
    {
      "a": {
        "b": {
          "c": true
        }
      }
    }

Instead of:

    # this is the expected result
    {"a.b.c": True}

* Update changelog

(cherry picked from commit a0b2db2)
@mergify mergify bot requested a review from a team as a code owner February 7, 2023 14:45
@mergify mergify bot added the backport label Feb 7, 2023
@mergify mergify bot assigned zmoog Feb 7, 2023
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Feb 7, 2023
@botelastic
Copy link
Copy Markdown

botelastic bot commented Feb 7, 2023

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

@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Feb 7, 2023

💚 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-02-07T20:51:02.167+0000

  • Duration: 67 min 9 sec

Test stats 🧪

Test Results
Failed 0
Passed 3434
Skipped 305
Total 3739

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

Copy link
Copy Markdown
Contributor

@zmoog zmoog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove unrelated CHANGELOG entries

@zmoog zmoog merged commit 9ded705 into 7.17 Feb 8, 2023
@zmoog zmoog deleted the mergify/bp/7.17/pr-34478 branch February 8, 2023 09:07
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.

2 participants