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.1](backport #31048) Put data stream so there is no need for additional permissions #31186

Merged
merged 1 commit into from
Apr 6, 2022

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 6, 2022

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

## What does this PR do?

This PR adds a new step to loading templates. Now not only the template is loaded, but the data stream is created as well. Given that users might load templates from JSON file that are not data streams, I added a new option called `setup.template.json.data_stream`. It has to be set, if the JSON template is a data stream.

## Why is it important?

Without this change users needed more permissions to publish events. Now `create_doc` priviledge is  enough to publish events to the data stream.

Closes #30647
Closes #30567

(cherry picked from commit 5cdb312)
@mergify mergify bot requested review from a team as code owners April 6, 2022 14:22
@mergify mergify bot added the backport label Apr 6, 2022
@mergify mergify bot assigned kvch Apr 6, 2022
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 6, 2022
@botelastic
Copy link

botelastic bot commented Apr 6, 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

  • Start Time: 2022-04-06T14:22:29.131+0000

  • Duration: 148 min 56 sec

Test stats 🧪

Test Results
Failed 0
Passed 25251
Skipped 1941
Total 27192

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

@cmacknz cmacknz merged commit e6e29cf into 8.1 Apr 6, 2022
@mergify mergify bot deleted the mergify/bp/8.1/pr-31048 branch April 6, 2022 17:13
# 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.

3 participants