feat: provision retirement states during lms setup #101
+12
−0
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.
We would like new devstack instances to better support the user retirement pipeline out of the box after provisioning.
This PR adds a new provisioning script that will be run during LMS setup. It runs the
populate_retirement_states
management command in order to build theuser_api_retirementstate
table. Without this, user deletion will fail, as the system doesn't understand what to do when retiring user accounts.I've completed each of the following or determined they are not applicable: