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

[Filebeat] AWS Input - Document bucket_list_prefix #28527

Merged
merged 1 commit into from
Oct 19, 2021
Merged

[Filebeat] AWS Input - Document bucket_list_prefix #28527

merged 1 commit into from
Oct 19, 2021

Conversation

aspacca
Copy link

@aspacca aspacca commented Oct 19, 2021

Docs

What does this PR do?

Add missing documentation about bucket_list_prefix introduced in #28252

Why is it important?

Users using a custom config with an AWS S3 input will find the documentation about the new feature

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.

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Relates #28252

Use cases

Screenshots

Logs

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Oct 19, 2021
@mergify
Copy link
Contributor

mergify bot commented Oct 19, 2021

This pull request does not have a backport label. Could you fix it @aspacca? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v./d./d./d is the label to automatically backport to the 7./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

@mergify mergify bot added the backport-skip Skip notification from the automated backport with mergify label Oct 19, 2021
@aspacca aspacca added backport-v7.16.0 Automated backport with mergify Team:Integrations Label for the Integrations team labels Oct 19, 2021
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Oct 19, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations (Team:Integrations)

@mergify mergify bot removed the backport-skip Skip notification from the automated backport with mergify label Oct 19, 2021
@aspacca aspacca requested a review from kaiyan-sheng October 19, 2021 11:41
@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: 2021-10-19T11:40:52.072+0000

  • Duration: 29 min 56 sec

  • Commit: 135ba9b

❕ 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.

@aspacca aspacca merged commit 21dca31 into elastic:master Oct 19, 2021
mergify bot pushed a commit that referenced this pull request Oct 19, 2021
aspacca pushed a commit that referenced this pull request Oct 19, 2021
(cherry picked from commit 21dca31)

Co-authored-by: Andrea Spacca <[email protected]>
Icedroid pushed a commit to Icedroid/beats that referenced this pull request Nov 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-v7.16.0 Automated backport with mergify Team:Integrations Label for the Integrations team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants