Actions
Tracker #19454
openMark plugin migrations to be able to run them separately for each plugin.
% Done:
0%
Description
Rails migrations have a nice feature called "scope" (as described here: http://edgeguides.rubyonrails.org/engines.html#engine-setup).
This feature enables running only migrations that belong to a certain scope.
I propose using this feature in our plugins to mark plugin's migrations, so we will be able to migrate up or down only those migrations. Effectively it will enable us to uninstall every table that belonged to a plugin.
In order to use scopes, migrations should be named accordingly: [timestamp]_[migration_name].[scope].rb (the change is adding the ".scope" to filename).
Once all the migrations are named that way, we can migrate them up or down using:
# set up a plugin: rake db:migrate SCOPE=my_plugin # remove the plugin from DB: rake db:migrate SCOPE=my_plugin VERSION=0
Updated by Shimon Shtein about 8 years ago
- Related to Feature #3588: Uninstall plugins - from GUI or command line added
Updated by The Foreman Bot about 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/4509 added
Updated by Dominic Cleal almost 8 years ago
- Has duplicate Feature #16595: Add scoping to plugin migrations. added
Updated by Shimon Shtein almost 8 years ago
- Tracker changed from Feature to Tracker
- Status changed from Ready For Testing to Assigned
Updated by Shimon Shtein almost 8 years ago
- Blocked by Feature #19589: Add an option to create plugin migrations with properly marked scope added
Actions