Update to "read_pipeline" permission in docs #26465
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I don't know in what version this was updated to be called "read_pipeline". but it is available through the roles settings in Kibana.
philippkahr
added
docs
cleanup
release-note:skip
botelastic
bot
added
the
needs_team
philippkahr
added a commit
that referenced
this pull request
Jun 24, 2021
As discussed in the PR #26465 the docs should reflect that read_pipeline is needed when using modules. Users usually just copy and paste the JSON payload and might experience failures when running any beat with modules.
💚 Build Succeeded
Expand to view the summary
Build stats
Trends 🧪❕ Flaky test reportNo test was executed to be analysed. |
|
Pinging @elastic/agent (Team:Agent) |
botelastic
bot
removed
the
needs_team
jsoriano
added
needs_team
|
Pinging @elastic/obs-docs (Team:Docs) |
botelastic
bot
removed
the
needs_team
|
This pull request doesn't have a |
dedemorton
approved these changes
Jun 24, 2021
There was a problem hiding this comment.
Looks good from a doc perspective, though I did not test the privilege to confirm it works.
This change will need to be forward-ported to master and 7.x. Do you want me to take care of that?
Note for future reference: select the master branch before you click the Edit link. That makes it easier for us to backport the changes. Thanks!
|
Hi @dedemorton |
|
Quick question before I merge this. Were you able to test the recommended privileges? I ran a quick test and got errors, but it's possible that I missed something. I don't have time to play security privilege whack-a-mole today. If you've tested and it worked, I will merge and backport. Thanks! |
|
hi ! yes I was able to set it like this on a 7.12.2 and upwards cluster. |
dedemorton
pushed a commit
to dedemorton/beats
that referenced
this pull request
Jun 29, 2021
I don't know in what version this was updated to be called "read_pipeline". but it is available through the roles settings in Kibana.
dedemorton
pushed a commit
to dedemorton/beats
that referenced
this pull request
Jun 29, 2021
I don't know in what version this was updated to be called "read_pipeline". but it is available through the roles settings in Kibana.
dedemorton
pushed a commit
that referenced
this pull request
Jun 29, 2021
As discussed in the PR #26465 the docs should reflect that read_pipeline is needed when using modules. Users usually just copy and paste the JSON payload and might experience failures when running any beat with modules.
dedemorton
pushed a commit
to dedemorton/beats
that referenced
this pull request
Jun 29, 2021
As discussed in the PR elastic#26465 the docs should reflect that read_pipeline is needed when using modules. Users usually just copy and paste the JSON payload and might experience failures when running any beat with modules.
dedemorton
pushed a commit
to dedemorton/beats
that referenced
this pull request
Jun 29, 2021
As discussed in the PR elastic#26465 the docs should reflect that read_pipeline is needed when using modules. Users usually just copy and paste the JSON payload and might experience failures when running any beat with modules.
dedemorton
added a commit
that referenced
this pull request
Jun 29, 2021
dedemorton
added a commit
that referenced
this pull request
Jun 29, 2021
As discussed in the PR #26465 the docs should reflect that read_pipeline is needed when using modules. Users usually just copy and paste the JSON payload and might experience failures when running any beat with modules. Co-authored-by: Philipp Kahr <philipp.kahr@elastic.co>
dedemorton
added a commit
that referenced
this pull request
Jun 29, 2021
As discussed in the PR #26465 the docs should reflect that read_pipeline is needed when using modules. Users usually just copy and paste the JSON payload and might experience failures when running any beat with modules. Co-authored-by: Philipp Kahr <philipp.kahr@elastic.co>
dedemorton
added a commit
that referenced
this pull request
Jun 29, 2021
mdelapenya
added a commit
to mdelapenya/beats
that referenced
this pull request
Jun 30, 2021
* master: (25 commits) fix: Force PLATFORMS environment variable when we build Elastic Agent dependencies on arm64 (elastic#26415) macos for metricbeat to run in the extended meta-stage (elastic#26573) Packaging: add arm7 platform in the main pipeline (elastic#26575) [Heartbeat] Skip flakey timer queue test (elastic#26592) Update to "read_pipeline" permission (elastic#26465) (elastic#26580) API keys do not reflect the need for read_pipeline (elastic#26466) (elastic#26582) Add Fleet agent.id to Agent monitoring data (elastic#26548) Add kinesis metricset (elastic#25989) Refactor of system/memory metricset (elastic#26334) Introduce httpcommon package in libbeat (add support for Proxy) (elastic#25219) [Filebeat] change multiline configuration in awss3 input to parsers (elastic#25873) docs: Hint for the error "Error extracting container id" (elastic#25824) [Docs] Fixed metricbeat redis exported field CPU descriptions (elastic#25846) (elastic#26496) Update urllib to 1.26.5. (elastic#26380) Update golang.org/x/crypto (elastic#26448) [Filebeat] Update Fortinet Ingest Pipeline (elastic#24816) Move parsers outside of filestream input so others can use them as well (elastic#26541) [Filebeat] Fix `threatintel.indicator.url.full` field not populating (elastic#26508) [Filebeat] Add network direction processor to Zeek and Suricata modules (elastic#24620) Logging code cleanup related to Nomad auto-discovery (elastic#26498) ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
I don't know in what version this was updated to be called "read_pipeline". but it is available through the roles settings in Kibana.
This change should be reflected across all beats docs.
Why is it important?
Users might try to copy and paste the permissions and receive errors or incompatibility in the future.