Add missing migrations for internal/external button model changes #3411
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.
Summary (required)
There was a missing migration when the internal and external button additions were made for the records page. See referenced PR: #3338. This PR backfills the missing migration file that were introduced in the 20191126 release.
I ran a diff between the migration file up on the cloud CMS server (dev-cloud-migration-107.txt) against the generated migration file in this PR and it matches exactly. So it should be safe to merge this migration with all the others.
Impacted areas of the application
List general components of the application that this PR will affect:
Related PRs
List related PRs against other branches:
How to test
./manage.py makemigrations