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

Tidy up provisioning and loadstatic thing #619

Merged
merged 1 commit into from
Aug 30, 2016
Merged

Conversation

ian-ross
Copy link
Contributor

Proposed changes in this pull request

  • Reinstate commented code in loadstatic management command.
  • Add a --force flag to the loadstatic management command. If static data database entities already exist, loadstatic will not make any changes unless this flag is supplied.
  • Bump django-jsonattrs version to 0.1.10 to pick up version with force flag in attribute type loading.
  • Reinstate 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 the aws-deploy.yml Ansible playbook, so static data loading will need to be performed as an additional step during deployments.

Follow up actions

None.

@ian-ross ian-ross force-pushed the tidying/loadstatic branch from 5bbc9c9 to fbf4842 Compare August 30, 2016 10:02
@amplifi
Copy link
Contributor

amplifi commented Aug 30, 2016

Looks good to me; ship it 👍

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

Successfully merging this pull request may close these issues.

3 participants