Closed adam-vessey closed 1 year ago
It seems like it's jumping through hoops to preserve a very edge (if not absurd) use case - where you'd deliberately install islandora_fits but then choose to not do the migration. Is there an argument that this behaviour is worth preserving? (or is this to prevent any changes to the expected behaviour/interface that might be used in workflows?)
@rosiel : Not quite? The demo
thing doesn't (or didn't?) do FITS: https://github.com/Islandora-Devops/islandora-playbook/blob/dev/vars/demo.yml ... so to avoid attempting to execute a migration in an environment that didn't have it, a variable was introduced. Now, similar kind of thing, where the --tag=islandora
is only valid if the migrations bear the tag, which is unknown in the demo
environment.
Tested and works on starter_dev
.
I'm struggling to test on demo
because of PHP conflicts, and the fact that we're possibly using the wrong branch of islandora_sandbox... but that's far beyond this ticket.
I'd say this ticket is ready to go. @adam-vessey any other concerns before taking it out of draft?
Nah, my only concern is that I hadn't actually run things myself... theoretical code was theoretical. :P
If it is indeed functional, then sure, let's do it!
Tested and works on starter_dev
.
I'm struggling to test on demo
- finally it ran, but some other issues popped up that are breaking demo anyway.
I'd say this ticket is ready to go. @adam-vessey any other concerns before taking it out of draft?
GitHub Issue: (link)
What does this Pull Request do?
A brief description of what the intended result of the PR will be and/or what problem it solves.
What's new?
A in-depth description of the changes made by this PR. Technical details and possible side effects.
How should this be tested?
A description of what steps someone could take to:
Additional Notes:
Any additional information that you think would be helpful when reviewing this PR.
Interested parties
Tag (@ mention) interested parties or, if unsure, @Islandora-Devops/committers