Hotfix greatuk 1662 local s3 implementation #3839
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
A bunch of setting changes to ensure great-cms can work in a local environment
Why
Migrating to DBT PaaS highlighted some issues in great-cms that needed fixing. The main issue was that we are unable to connect to an s3 bucket in DBT PaaS.
The changes in the PR are linked to changes in great-docker in a branch by the same name. The new docker set up uses Localstack to fire up a local s3 instance that can be used when developing locally.
Changes include new storage classes, management commands and setting configurations.
Workflow
Merging