sergehuber opened a new pull request, #910: URL: https://github.com/apache/unomi/pull/910
## Plain-language summary The existing migration test starts from a 1.6 snapshot with the full feature set already installed. That setup did not catch the 3.0 upgrade problems fixed in UNOMI-996 and UNOMI-997. This PR adds an integration test that seeds a small synthetic 3.0 data set over HTTP, runs `unomi:migrate 3.0.0` before Unomi starts, then checks the post-migration shape. ## What changed * New `Migrate30ToCurrentVersionIT`, registered first in `AllITs` / `CorePersistenceITs` so it runs before the 1.6 snapshot restore. * Seeds systemitems (shipped definition + user rule/segment), profile, geoname, cluster node and Salesforce configuration indices, then migrates. * Asserts: default tenant exists; user content stays out of system; geonames are system; cluster nodes and unknown indices use the configured tenant; every document has a tenant; the 4.0 `booleanCondition` wins over the seeded 3.0 marker; migration-mappings are present in the shell-commands bundle; the API key file names the real headers. * Correct the API key file text in `migrate-4.0.0-10-tenantInitialization.groovy` (`X-Unomi-Api-Key` / Basic auth) so it matches what Unomi actually accepts. ## Test plan * [x] `./build.sh --skip-unit-tests --no-javadoc --no-clean --integration-tests --single-test org.apache.unomi.itests.migration.Migrate30ToCurrentVersionIT` * [ ] CI green on Elasticsearch and OpenSearch jobs -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
