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

Making boto3 related configs vars available to be set in Django settings #60

Open
manjitkumar opened this issue Mar 27, 2021 · 1 comment

Comments

@manjitkumar
Copy link

Hey Contributors,
First of all I want to say this project has been a very useful component in a project I worked on recently.

I wanted to bring your attention to discuss the future plans or roadmaps for this project as I have a some ideas to discuss and see what you think of it and if it is something can be done I am happy to work on it and share a pull request to be reviewed 🙌

  1. Making boto3 configurations available to be set in django.conf.settings (prefixed: AWS_)

some of the django based libraries already acknowledges the settings variables and let user define it in their. i.e django-storages

I came across this error

CredentialRetrievalError
Error when retrieving credentials from iam-role: Credential refresh failed, response did not contain: access_key, secret_key, token, expiry_time

where set higher values for AWS_METADATA_SERVICE_NUM_ATTEMPTS & AWS_METADATA_SERVICE_TIMEOUT could have helped.

  1. A little bit work on the documentation of this project. I see it as a highly efficient and scalable piece of technology with a complete and effective alternative to celery (as celery is not recommended to be used with SQS) and still I came across so many projects and people who want to use AWS SQS for it's reliability and scalability but celery doesn't work that well as it does for other ampq based brokers.

For 2nd part, I want to connect with a core contributor who can help me understand the project in detail so I can start contributing to the improvements on documentation as well.

Looking forwarded to hearing from you guys.

@alexeyts
Copy link
Contributor

Hi @manjitkumar,
Thanks for your comments.

With regards to issue 1. - definitely makes sense!
We currently have only AWS_REGION and AWS_MAX_RETRIES defined, but ideally would expose all the possible configurations of boto3.
Should be also, and easy change, in case you want to contribute.

We regards to point 2 - I think it would help to have your questions written down, of what documentation is missing and what specifically you want to understand.

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

2 participants