Adds option for lazy connection to swift #97
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instead of connecting to SWIFT on storage init, this adds an option to allow the SWIFT connection to be created only when required.
Django takes great care to initialise Storage classes lazily, and so connecting on creation is generally a valid option. However there are some cases where this is difficult to do, e.g., when using
FileField.storage
, the Storage instance is instantiated on model import time, which can result in unintended SWIFT authentication/connections.Reviewer