Tracker #19454
open
Mark plugin migrations to be able to run them separately for each plugin.
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 over 7 years ago
- Related to Feature #3588: Uninstall plugins - from GUI or command line added
Updated by Dominic Cleal over 7 years ago
Isn't this the same as #16595?
In both cases, I think this needs filing against the plugin(s) you intend to change, not Foreman, unless there's a code change not mentioned that's required in Foreman.
Updated by The Foreman Bot over 7 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/4509 added
Updated by Shimon Shtein over 7 years ago
Thanks for finding the older issue - it's the same functionality I am talking about.
I think we can close the older one - this one is more informative.
This issue is about adding a generator to our framework, so the scope would be handled automatically for new migrations.
For example, by running the following command from foreman directory:
rails g plugin:migration test_migration --plugin-name=my_plugin
will generate a new migration file called 20170101000_test_migration.my_plugin.rb in plugin's db/migrate directory.
Updated by Dominic Cleal over 7 years ago
- Has duplicate Feature #16595: Add scoping to plugin migrations. added
Updated by Dominic Cleal over 7 years ago
I think we can close the older one - this one is more informative.
Done, please just do it next time.
Updated by
Updated by Shimon Shtein over 7 years ago
- Tracker changed from Feature to Tracker
- Status changed from Ready For Testing to Assigned
Updated by Shimon Shtein over 7 years ago
- Blocked by Feature #19589: Add an option to create plugin migrations with properly marked scope added
Updated by Shimon Shtein over 7 years ago
Changed this issue to track all the progress of marking migrations.
The work on core generator will be attached to http://projects.theforeman.org/issues/19589.
Updated by Tomer Brisker over 6 years ago
- Target version deleted (
1.13.3) - Triaged set to No