Is it still possible to specify different migration.yml files for development and deployed systems?
During development the ability to seed the NPL for integration tests is required, this is undesirable in deployed systems
Yes, using run-only
Well that’s not entirely true, as run-only is an element in the migration.yml but I think I figured it out.
The correct answer is more like “One doesn’t need multiple migrations files as one can control what is run by using run-only”.
1 Like
Yes, sorry for the vague answer, that is indeed what I meant.