Revert: Grant migrator privileges even when the user already exists#8313
Revert: Grant migrator privileges even when the user already exists#8313CarolineDenis wants to merge 1 commit into
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
combs-a
left a comment
There was a problem hiding this comment.
I wrote these testing instructions, but they may need to be added onto if anyone spots any additional coverage needed!
New database:
- Check the
specify7container logs and make sure there are no migration errors. - Make sure that it's opening the Specify 7 initial database setup screen.
Previously existing database (used pre v7.12):
- Check the
specify7container logs and make sure there are no migration errors. - Make sure that it's opening the Specify 7 login page.
New database worked as expected.

Was able to create a new database with no issues, but ran into an issue with the Specify app user when attempting to open an old database. Used the same database as I did in the originally reported issue.
Fixes #8305
Checklist
self-explanatory (or properly documented)
specify7/specifyweb/specify/management/commands/run_key_migration_functions.py
Line 50 in ea04665
Testing instructions
specify_migrator* andspecify_user* already created in MySQL.MIGRATOR_NAMEandAPP_USER_NAMEin the .env file..envfile so that the DATABASE_NAME is one that does not exist yet.specify7container logs and make sure there are no migration errors..envfile so that the DATABASE_NAME is one that does exist and was not previously opened in v7.12.specify7container logs and make sure there are no migration errors.