feature/handle-initial-migration

[tomchkk]

Overview

• I have performed a self review of my code
• I have made corresponding changes to the documentation
• I have commented my code, particularly in hard-to-understand areas
• I have added sufficient logging

• New and existing tests pass locally with my changes
• The code modified as part of this PR has been covered with tests

• The API spec has been modified inline with the changes in this PR

Problem statement

Running a mutex migration using the default database store requires the existence of a table to store cache locks. This present a chicken and egg problem if attempting to use the --mutex option.

Solution

This PR wraps the main call to run the MutexMigrationCommand class in a try/catch block, handling the existing DatabaseCacheTableNotFoundException to allow a standard migration to be run in the event that the exception is thrown.

Dependencies

n/a

Test procedures

n/a

Links

Deployment

Migrations

No

Environment variables

n/a

Deployment notes

n/a

[tomchkk]

@kubatek94 - looking at this initially I felt that it wasn't worth adding any additional command options but just to allow the --mutex option to always work. I'm open to differences of opinion though, of course 😊

[kubatek94]

Happy days @tomchkk! I was more in favour of such solution as well, but thought you would prefer an extra option instead so didn't suggest that haha :D Nice change!

[tomchkk]

Happy days @tomchkk! I was more in favour of such solution as well, but thought you would prefer an extra option instead so didn't suggest that haha :D Nice change!

Should have just done it this way in the first place 😂