Invalid migration scripts for job profiles

Verified on vagrant-box:

Hi ,

did you use loadSample and loadReference (https://github.com/folio-org/okapi/blob/master/doc/guide.md#install-parameter-tenantparameters) during mod-data-export updating from release to release (namely, from Kiwi to Lotus)? I mean, there are several options: 1) Module is enabled in OKAPI with loadSample = false and DB is migrated by using migration scripts; 2) Module is enabled in OKAPI with loadSample = true and after that DB is migrated by using migration scripts; 3) Initially DB is migrated by using migration scripts and after that module is enabled in OKAPI.

This is critical to understand because executing the database migration without requesting the load sample data, or doing the migration after enabling the module, lead to this problem particular problem.

I can add missed profiles in the migration scripts but I assume this is overkill because we already have this mechanism in the framework of Tenant API with using loadSample=true.

CC

UPD: 

I've implemented and verified migration scripts that add holdings mapping and job profiles and opened pull-request. I assume this is the easiest way unlike changing the standard pipeline for releasing of new modules.

Thanks, 

Slava