Use FacilityUser instead of AUTH_USER_MODEL in migrations #11984
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
Using settings.AUTH_USER_MODEL breaks migrations when using kolibri in context where this model points to something different than FacilityUser. For example, PortalUser in KDP
References
For the future, any time migrations are created that relate to the user model, we should ensure that they point to FacilityUser. When changing AUTH_USER_MODEL, we may not want the kolibri models to be used for this new user type.
Reviewer guidance
Migrations should continue working fine
Testing checklist
PR process
Reviewer checklist
yarn
andpip
)