...
- It is very time-consuming and requires a lot of manual effort to clean up old Kafka topics after upgrading DI modules to the new FOLIO release. Migration script to clean up old topics will greatly enhance upgrades.
- Some of the job profiles are very complex(Create, Update) and there is no easy way to copy existing Data Import Job profile from one FOLIO tenant to another or from one FOLIO release to another. We have to manually create a Job profile either from UI or backend(database - requires a lot of effort in aligning metadata). It would save a lot of time and effort if there is a way to export the existing Job profile from tenant 1 and import the same to tenant 2.
- Stuck jobs do not provide end-users and DevOps insightful information to troubleshoot. Only having to dig through logs when a problem might be spotted. There was a JIRA to end the job with an error status and to surface the issue. Additionally perhaps other relevant errors from the modules could be collected and displayed in a "detail" link/button for technical users to examine.