Preventing Duplicate Migrations on the Same Shard and fix

[Prathamesh Vichare]

Hello @thiagopradi and fellow members,

I hope this message finds you well. I am reaching out regarding an issue I encountered while running migrations in ar-octopus (version 0.10.2). In the course of my work, I observed an unexpected behavior when executing migrations, specifically with the migration count and process.

To provide some context, I added a new migration file to my application, but upon initiating the migration process, I noticed that it was attempting to run migrations for all 1600 migration files present in my application, instead of just the new one I had introduced.

In light of this, I have created an issue on the ar-octopus GitHub repository to document this problem and its impact. You can find the issue raised at: GitHub Issue #581.

Taking a proactive approach to address this issue, I've also prepared a proposed solution and submitted a pull request for review. The pull request, labeled PR #580, contains the necessary changes to rectify the migration behavior anomaly.

I'm reaching out to the community to seek feedback on the proposed fix. Your insights and expertise are highly valuable, and I would greatly appreciate any feedback or suggestions you may have regarding the appropriateness and effectiveness of this solution.

Thank you for your time and consideration. I look forward to hearing your thoughts on this matter.

Best regards,

Prathamesh Vichare