How to generate data-migration report
Significant changes were implemented on 7/28/2025
Report Available on demand.
***Please follow up instructions strictly***
***NO ADDITIONAL ACTIONS REQUIRED***
Starting from the date above, there is NO LONGER a dedicated pipeline for report generation process. To generate report, standard createNamespaceFromBranch job will be used.
Involved pipelines:
Required actions:
Trigger createNamespaceFromBranch with required parameters (described below)
Wait some time, until env is built
Access report via URL: Report
(Optional) if needed make a copy of report by saving it to local storage
Destroy environment to optimize infratructure cost expencies
REQUIRED PARAMETERS:
NAME | VALUE |
|---|---|
PLATFORM | EUREKA |
CLUSTER | folio-eperf |
NAMESPACE | data-migration |
BRANCH | snapshot |
DATA | should be checked(selected) |
POSTGRESQL | aws(from drop-down) |
DB_VERSION | 16.6 |
EXAMPLES OF PARAMETERS FOR ENV CREATION:
EXAMPLES OF PARAMETERS FOR ENV DELETION:
If any of additional parameters are not outlined in the table and screenshots above, that’s mean defaults values of those parameters are OK and DO NOT REQUIRE MODIFICATION, please leave it AS IS.
CAUTION: webpage is JavaScript based report, which automatically fetching source data from built environment, if env is not available, report will not show results!
To see the report, open the link - Report, you’ll see something as below:
Click on “fetchData” button, if operation succeeded, unique UUID will be displayed:
That is UUID of entitlement, click on it and then report will be generated:
Ramsons to Sunflower(pre) migration report below: