Migration: add a user_id column to the kudos table, indexed but not (yet) unique, unused:
Add a migration as usual, to be used in dev and CI environments.
Add a pt-online-schema-change command in the PR description to be run on staging and beta.
No need to use a foreign key constraint because the kudos should stick around as guest kudos when users are deleted.
No downtime needed because the column is unused.
To test this, a database admin should run the migration (up, down, and back up) and then testers should confirm kudos still work as expected.
So we the migration is set to done on staging.
Done the migration down
then I should put it back up when you wish
Oh, good idea, let's check
Left guest kudos on https://test.archiveofourown.org/works/151?view_adult=true
guest and logged in kudos work for me while migrated down
I did https://test.archiveofourown.org/works/152
say when to go back up
So I think we can migrate up and mumble can test that and we'll be all done
i also kudosed something without problems (as guest and logged in) (edited)
so yes, bring it
i just went to this work, which i have never seen before: https://test.archiveofourown.org/works/144 and tried to leave a guest kudo and it says "You have already left kudos here. :)"
i could kudos it logged in
tl;dr staging is set up a bit funky so guest kudos were recording the IP of the front ends. Nothing deploy blocking and it won't happen on production, so we're all set!
james is starting the migration on production now, so setting this to Deployed