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

"rename" CinderJob.decision_id to decision_cinder_id #22000

Merged

Conversation

eviljeff
Copy link
Member

fixes mozilla/addons#9499 - just renames the column from decision_id to decision_cinder_id.

@eviljeff eviljeff requested a review from KevinMind March 12, 2024 10:12
Copy link
Contributor

@KevinMind KevinMind left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assuming we test this via CI but looks good to me.

@eviljeff
Copy link
Member Author

Assuming we test this via CI but looks good to me.

yes, apart from the RunPython migration - as the test setup starts with an empty database it doesn't fully test the case of migrating existing data. But it's super trivial so it doesn't concern me.

If you did want to test this locally:

  • you'd need at least one CinderJob with a decision_id set (would need either manually setting via django admin before the patch was checked out, or via db admin after)
  • then run ./manage.py migrate abuse (or make update_db if you wanted to run all the migrations)
  • check that CinderJob.decision_cinder_id now has the value that decision_id had.

@eviljeff eviljeff merged commit 5f84d0c into mozilla:master Mar 12, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants