-
Notifications
You must be signed in to change notification settings - Fork 64
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
Add ability to set endpoint_url from AWS_ENDPOINT_URL env variable #193
Conversation
…ery useful for localstack while waiting for upstream PR from boto3: boto/boto3#2746
Looks good to me! Test would be great, and then an issue to track removing if/when the upstream issue is resolved. |
Codecov Report
@@ Coverage Diff @@
## master #193 +/- ##
========================================
- Coverage 94.3% 93.9% -0.5%
========================================
Files 21 21
Lines 1197 1198 +1
========================================
- Hits 1129 1125 -4
- Misses 68 73 +5
|
Here's that test |
Added the issue as well |
Test looks good. Can you make sure linting passes? ( |
Done, not sure why the live tests would be failing though. Doesn't seem to be related to this change. |
@kabirkhan yeah, i think that is just that PRs from forks can't use the secrets so live tests can't authenticate. i'll do some digging to see how we enable that. |
Dropped these changes on their own branch so we can run the live tests there to confirm |
) (#195) * Add ability to set endpoint_url from AWS_ENDPOINT_URL env variable. Very useful for localstack while waiting for upstream PR from boto3: boto/boto3#2746 * add test * rm print * lint Co-authored-by: Kabir Khan <[email protected]>
Hey guys! Long time :)
Loving this package so far. One minor convenience that might be easier to merge here than this ridiculous upstream PR for the boto3 library.
Allows setting the endpoint_url from the AWS_ENDPOINT_URL env variable while waiting for the upstream PR from boto3: boto/boto3#2746
I'll add a test if the idea works for you guys