Bugfix to ligoauth migrations
Fixing two migrations - ligoauth 0004: properly delete User instance for gstlal-spiir-gpu, not just LocalUser/RobotUser - ligoauth 0013: deleted, since gstlal-spiir-gpu has been deleted, we don't need to create a RobotUser instance for it
Showing
- gracedb/ligoauth/migrations/0004_update_gstlal_spiir_account.py 3 additions, 1 deletion...b/ligoauth/migrations/0004_update_gstlal_spiir_account.py
- gracedb/ligoauth/migrations/0013_make_gstlal-spiir-gpu_robotuser.py 0 additions, 39 deletions...goauth/migrations/0013_make_gstlal-spiir-gpu_robotuser.py
- gracedb/ligoauth/migrations/0013_x509cert_subject_longer.py 1 addition, 1 deletiongracedb/ligoauth/migrations/0013_x509cert_subject_longer.py
- gracedb/ligoauth/migrations/0014_add_new_dashboard_cert.py 1 addition, 1 deletiongracedb/ligoauth/migrations/0014_add_new_dashboard_cert.py
- gracedb/migrations/guardian/0002_authorize_users_to_populate_pipelines.py 3 additions, 2 deletions...ns/guardian/0002_authorize_users_to_populate_pipelines.py
Please register or sign in to comment