Run Tag based migrations so that we get Mirador term and there's less reason to fork site template. #38
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.
We used to run islandora migrations as a "group" but (to simplify greatly) Drupal stopped supporting migration groups. What we should be using now are tags. Most islandora migrations are tagged with "islandora".
However at some point, we made the (IMO, wrong) choice to not use tags in the site template but to name the migrations that we wanted to run.
This prevents other modules - like islandora mirador - from creating migrations that need to get run during provisioning.
This PR makes the Site Template on par with ISLE-DC by running the migrations with
--tag=islandora
. In practice, this means you'll get the Mirador term in the "Islandora Display" vocabulary.It would be good to make more people aware that "we run migrations tagged with
islandora
on provisioning` to empower people to do what they want to without having to fork our provisioning systems.