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

feat: provision retirement states during lms setup #101

Merged
merged 1 commit into from
Jan 22, 2025

Conversation

justinhynes
Copy link
Member

@justinhynes justinhynes commented Jan 22, 2025

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 the user_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:

  • Made a plan to communicate any major developer interface changes (or N/A)

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 the `user_api_retirementstate` table. Without this, user deletion will fail, as the system doesn't understand what to do when retiring user accounts.
@justinhynes justinhynes merged commit 72d3b2a into master Jan 22, 2025
13 checks passed
@justinhynes justinhynes deleted the jhynes/APER-3168_provision-retirement-states branch January 22, 2025 18:22
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.

2 participants