Skip to content

[8.16](backport #41495) x-pack/filebeat/input/awss3: support for Access Point ARN#41688

Merged
chemamartinez merged 4 commits into8.16from
mergify/bp/8.16/pr-41495
Nov 22, 2024
Merged

[8.16](backport #41495) x-pack/filebeat/input/awss3: support for Access Point ARN#41688
chemamartinez merged 4 commits into8.16from
mergify/bp/8.16/pr-41495

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Nov 19, 2024 •
edited by zube bot
Loading

Proposed commit message

Added a new option access_point_arn to the AWS S3 input as an alternative to the bucket ARN to access S3 buckets.

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.

Related issues

This is an automatic backport of pull request #41495 done by [Mergify](https://mergify.com).

@chemamartinez @mergify
x-pack/filebeat/input/awss3: support for Access Point ARN (#41495)
f461d90 
Added a new option access_point_arn to the AWS S3 input as an alternative to the bucket ARN to access S3 buckets.

(cherry picked from commit 301988d)
@mergify mergify bot added the backport label Nov 19, 2024
@mergify mergify bot requested review from a team as code owners November 19, 2024 15:45
@mergify mergify bot requested review from mauri870 and rdner and removed request for a team November 19, 2024 15:45
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Nov 19, 2024
@pierrehilbert
Copy link
Copy Markdown
Contributor

pierrehilbert commented Nov 19, 2024

@chemamartinez could you please fix the changelog entry?
Please don't merge this yet as the feature freeze for 8.16.1 was yesterday

@pierrehilbert pierrehilbert added the Team:Cloud-Monitoring Label for the Cloud Monitoring team label Nov 20, 2024
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Nov 20, 2024
@mergify
Copy link
Copy Markdown
Contributor Author

mergify bot commented Nov 20, 2024

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/8.16/pr-41495 upstream/mergify/bp/8.16/pr-41495
git merge upstream/8.16
git push upstream mergify/bp/8.16/pr-41495

@chemamartinez chemamartinez enabled auto-merge (squash) November 22, 2024 16:57
@chemamartinez chemamartinez merged commit dcad799 into 8.16 Nov 22, 2024
@chemamartinez chemamartinez deleted the mergify/bp/8.16/pr-41495 branch November 22, 2024 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mauri870 mauri870 mauri870 approved these changes

@chemamartinez chemamartinez chemamartinez approved these changes

@rdner rdner Awaiting requested review from rdner rdner is a code owner automatically assigned from elastic/elastic-agent-data-plane

Assignees

@chemamartinez chemamartinez

Labels

backport Team:Cloud-Monitoring Label for the Cloud Monitoring team

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@pierrehilbert @mauri870 @chemamartinez