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

[libbeat] Fix script processor examples in docs #30226

Merged
merged 1 commit into from
Feb 7, 2022

Conversation

andrewkroh
Copy link
Member

What does this PR do?

Fixes script processor examples in docs. The docs show id but the field is named tag.

Why is it important?

Examples should be correct.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

The docs show `id` but the field is named `tag`.
@andrewkroh andrewkroh added docs libbeat backport-v8.0.0 Automated backport with mergify backport-v8.1.0 Automated backport with mergify backport-v8.2.0 Automated backport with mergify backport-7.17 Automated backport to the 7.17 branch with mergify labels Feb 4, 2022
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Feb 4, 2022
@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-02-04T18:59:20.045+0000

  • Duration: 24 min 9 sec

❕ Flaky test report

No test was executed to be analysed.

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

@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Feb 4, 2022
@elasticmachine
Copy link
Collaborator

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@andrewkroh andrewkroh merged commit 32adc13 into elastic:main Feb 7, 2022
mergify bot pushed a commit that referenced this pull request Feb 7, 2022
The docs show `id` but the field is named `tag`.

(cherry picked from commit 32adc13)
mergify bot pushed a commit that referenced this pull request Feb 7, 2022
The docs show `id` but the field is named `tag`.

(cherry picked from commit 32adc13)
mergify bot pushed a commit that referenced this pull request Feb 7, 2022
The docs show `id` but the field is named `tag`.

(cherry picked from commit 32adc13)
andrewkroh added a commit that referenced this pull request Feb 7, 2022
The docs show `id` but the field is named `tag`.

(cherry picked from commit 32adc13)

Co-authored-by: Andrew Kroh <[email protected]>
andrewkroh added a commit that referenced this pull request Feb 7, 2022
The docs show `id` but the field is named `tag`.

(cherry picked from commit 32adc13)

Co-authored-by: Andrew Kroh <[email protected]>
andrewkroh added a commit that referenced this pull request Feb 7, 2022
The docs show `id` but the field is named `tag`.

(cherry picked from commit 32adc13)

Co-authored-by: Andrew Kroh <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-7.17 Automated backport to the 7.17 branch with mergify backport-v8.0.0 Automated backport with mergify backport-v8.1.0 Automated backport with mergify backport-v8.2.0 Automated backport with mergify docs libbeat Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants