Add option to ignore module migrations #126
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a
migrations.ignoreconfiguration key to exclude specified modules from the migration process.Includes a test to verify the functionality.
Hello! Thanks for this great package.
I'm proposing this change to introduce more granular control over the migration process in modular applications.
In complex projects, there's often a need to separate the "core" application migrations from those belonging to specific modules that might be enabled or set up on-demand. For example, one might want to run the main migrations during the initial deployment, but defer the migrations of certain modules to be executed later by a separate process or command.
This feature provides that flexibility by allowing developers to easily exclude certain modules from the default php artisan migrate command. This makes the package even more powerful for managing different deployment scenarios or workflows where not all modules should be migrated at the same time.
I believe this will be a valuable addition for others who need to manage their module migrations in a more controlled manner.
Thanks for your consideration