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.

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

Cherry-pick to 7.x: API keys do not reflect the need for read_pipeline (#26466) #26581

Merged
merged 1 commit into from
Jun 29, 2021

Conversation

dedemorton
Copy link
Contributor

Backports the following commits to 7.x:

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.
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jun 29, 2021
@dedemorton dedemorton added docs Team:Docs Label for the Observability docs team labels Jun 29, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/obs-docs (Team:Docs)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jun 29, 2021
@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

Expand to view the summary

Build stats

  • Build Cause: Pull request #26581 opened

  • Start Time: 2021-06-29T17:45:27.007+0000

  • Duration: 21 min 19 sec

  • Commit: 692adba

Trends 🧪

Image of Build Times

❕ Flaky test report

No test was executed to be analysed.

@dedemorton dedemorton merged commit 7de4b31 into elastic:7.x Jun 29, 2021
@dedemorton dedemorton deleted the backport/7.x/pr-26466 branch June 29, 2021 22:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport docs Team:Docs Label for the Observability docs team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants