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
[FEATURE] Enable passing boto3 options to TupleS3StoreBackend #1691
[FEATURE] Enable passing boto3 options to TupleS3StoreBackend #1691
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #1691 +/- ##
===========================================
- Coverage 77.85% 77.84% -0.02%
===========================================
Files 135 135
Lines 15680 15692 +12
===========================================
+ Hits 12208 12215 +7
- Misses 3472 3477 +5
Continue to review full report at Codecov.
|
9a16e68
to
ed628fe
Compare
ed628fe
to
79bd6f7
Compare
@alexsherstinsky Is this related to the boto change you just merged in #2364 ? How should we proceed with this PR here? |
…toreBackend (Thanks for great-expectations#1691 to @mgorsk1!) (great-expectations#2371) * LINT * Adding possibility to pass boto3_options to TupleS3StoreBackend -- thanks to PR 1691 by mgorsk1 (Community Contributor). * PR note in changelog.
…toreBackend (Thanks for great-expectations#1691 to @mgorsk1!) (great-expectations#2371) * LINT * Adding possibility to pass boto3_options to TupleS3StoreBackend -- thanks to PR 1691 by mgorsk1 (Community Contributor). * PR note in changelog.
Changes proposed in this pull request:
After submitting your PR, CI checks will run and @tiny-tim-bot will check for your CLA signature.
For a PR with nontrivial changes, we review with both design-centric and code-centric lenses.
In a design review, we aim to ensure that the PR is consistent with our relationship to the open source community, with our software architecture and abstractions, and with our users' needs and expectations. That review often starts well before a PR, for example in github issues or slack, so please link to relevant conversations in notes below to help reviewers understand and approve your PR more quickly (e.g.
closes #123
).Previous Design Review notes:
Thank you for submitting!