Tidy up provisioning and loadstatic thing #619
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.
Proposed changes in this pull request
loadstatic
management command.--force
flag to theloadstatic
management command. If static data database entities already exist,loadstatic
will not make any changes unless this flag is supplied.django-jsonattrs
version to 0.1.10 to pick up version withforce
flag in attribute type loading.data
provisioning role for development only to ensure that newly created development VMs have the appropriate static data loaded.When should this PR be merged
Any time.
Risks
Low to none, but reviewer (@amplifi) should check that the Ansible provisioning steps that will run during deployment and redeployment will produce the expected results. In particular, the
loadstatic
command is now not run from theaws-deploy.yml
Ansible playbook, so static data loading will need to be performed as an additional step during deployments.Follow up actions
None.