Update problem-builder requirement to 2.6.5patch2 to migrate keys. - #15862
Conversation
|
Thanks for the pull request, @jcdyer! It looks like you're a member of a company that does contract work for edX. If you're doing this work as part of a paid contract with edX, you should talk to edX about who will review this pull request. If this work is not part of a paid contract with edX, then you should ensure that there is an OSPR issue to track this work in JIRA, so that we don't lose track of your pull request. |
|
Just to make sure the steps forward on this are clear:
I can edit the above if there are more appropriate people to take on the particular tasks. |
|
Just noticed @fredsmith was not tagged as a reviewer on this PR. Just tagged him, that should put this on his radar to review. |
|
Thanks. I didn't realize you were using that functionality now. |
|
Test run on stage running now. |
|
@feanil Was the test successful? |
|
Test in stage was successful. This was deployed to production today. If I get some time this afternoon, I'll try to kick off the production migration before the weekend otherwise we'll kick it off next week. |
|
I've started the migration in production. At the current rate, it looks like it should finish in under an hour. @jcdyer Once it's done, I think what we'll need, is to make a PR that removes the old column from the model but don't add the migration. Followed by the addition of the migration that will remove the old column. Sound right? |
|
@jcdyer Migration complete in production. |
|
That sounds right. |
@feanil @fredsmith @bradenmacdonald
This pulls in open-craft/problem-builder#160, which provides a new script to run the key migration.