-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[8.6](backport #33559) Add backup to bucket functionality #34098
Conversation
* Add backup to bucket functionality Adds a functionality to backup processed files to another or the same bucket with an optional prefix. If enabled it will delete files from the source bucket. * Add documentation for backup_to_bucket configuration parameters * Add configuration to reference config file * Revert "Add configuration to reference config file" This reverts commit da59387. * Add back reference config changes without whitespace changes * fix typo that makes linter fail * change reference config the right way * Add later finalizing, missing tests for now * Add code review feedback & unit tests * Try fix G601 error * Fix last code review feedback * Add missing unit test * add entry to changelog * rename to , add permissions required for backup feature in docs * fix integration tests Co-authored-by: Andrea Spacca <andrea.spacca@elastic.co> (cherry picked from commit 5df1895) # Conflicts: # x-pack/filebeat/input/awss3/input.go # x-pack/filebeat/input/awss3/metrics.go
SonarCloud Quality Gate failed. 0 Bugs No Coverage information |
This pull request is now in conflicts. Could you fix it? 🙏
|
@aspacca I saw that you reviewed the original PR, may you have a look at this backport too? |
@endorama sure thing! |
This is an automatic backport of pull request #33559 done by Mergify.
Cherry-pick of 5df1895 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
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>
branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com