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

[s3] Allow S3-compatible endpoints, expose more options #2759

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nanderson94
Copy link

Closes #2758

This change exposes many more configuration options of boto3 to the user. This has the primary intent of allowing S3-Compatible services to be used, but I also carried-through FIP and Dualstack endpoint selection.

Checklists

Pre-Review Checklist

  • this PR does NOT contain credentials of any kind, such as API keys or username/passwords (double check config.yml.example)
  • this PR has a meaningful title
  • this PR links to all relevant github issues that it fixes or partially addresses
  • if there is no GH issue, please create it. Each PR should have a link to an issue
  • this PR has a thorough description
  • Covered the changes with automated tests
  • Tested the changes locally
  • Added a label for each target release version (example: v7.13.2, v7.14.0, v8.0.0)
  • Considered corresponding documentation changes
  • Contributed any configuration settings changes to the configuration reference
  • if you added or changed Rich Configurable Fields for a Native Connector, you made a corresponding PR in Kibana

Release Note

The S3 Connector now exposes options to support S3-Compatible object storage providers.

@nanderson94 nanderson94 requested a review from a team August 20, 2024 22:04
Copy link

❌ Author of the following commits did not sign a Contributor Agreement:
379fe6c

Please, read and sign the above mentioned agreement if you want to contribute to this project

Copy link
Contributor

@navarone-feekery navarone-feekery left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution!
Could you add some unit tests to cover the new configurations to the test file?
I think some good tests would be:

  1. ensuring self.s3_endpoint_url is assigned the right value in all circumstances
  2. ensuring self.config initializes for all the options for new configs s3_addressing_style, aws_use_fips_endpoint, and aws_use_dualstack_endpoint.

"aws_use_dualstack_endpoint": {
"display": "toggle",
"label": "Use Dualstack Endpoints",
"order": 7,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you go through the order values for the configurations after this and update them?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[s3] Allow usage of S3-Compatible endpoints
2 participants