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

Support URI string parameter for all WebSocket backends #100

Closed
jordaneremieff opened this issue May 4, 2020 · 1 comment
Closed

Support URI string parameter for all WebSocket backends #100

jordaneremieff opened this issue May 4, 2020 · 1 comment

Comments

@jordaneremieff
Copy link
Collaborator

Only the postgresql backend currently supports passing a single stringuri connection parameter, but it'd be a lot easier to use and customize the parameters if all the backends used a uri parameter.

SQLite, PostgreSQL, and Redis will be easy enough since the libs I use already accept them:

sqlite://<file_path>
postgresql://
redis://
rediss://

The backends that rely on Boto3 requests (S3, dynamodb) will need to be parsed first, but I figure something like this wouldn't be too difficult to implement:

s3://<bucket-name>/<key>?region=<region>
dynamodb://<table_name>?region=<region>&endpoint_url=<endpoint-url>

On a side-note: I should also document the behaviour of S3/dynamodb calls when inside a VPC.

@jordaneremieff
Copy link
Collaborator Author

Closed by #103

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

No branches or pull requests

1 participant