Implement Site's logo management via AWS S3 adapter #169
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.
Connects to #109.
Release notes
Releasing this one depends on #170.
What does this PR do?
This PR introduces a small library to abstract file upload operations, and integrates it into the Admin's Site management Form object to allow attaching a file from the UI and storing the
public_url
returned by the adapter.The first and only available adapter is AWS S3, which needs to be configured via environment variables, as usual. These environment vars are needed at the time being:
Once the S3 bucket is available and the AWS credentials are reachable from the app instance, an upload process will be performed every time the User submits a new file. All files are kept from now in a UUID format file names:
How should this be manually tested?
Get into a Site edit view within the Admin namespace, and submit a new logo in the file field. In the next GET request, the new logo should be shown right above the file field is rendered: