Feature #29745
Updated by Eric Helms about 5 years ago
The installer keeps answer and config file migrations per scenario. Often this results in the same migration being written multiple times if its a change to a module that exists across multiple scenarios. The proposal here is to reduce this down to a single set of migrations that apply to all scenarios where the migrations are coded to ensure they handle missing modules properly if a scenario does not have it present.