Need to:

• Develop a job that can run through the exported data and import it to Relations
  • This depends on RHCLOUD-35455
  • Usually done through admin REST API on Notifications
• (Optionally) Export all necessary data (integration ID, org ID) from notifications in some sort order (this may warrant another column e.g. creation date)
  • Run the job above to import this data if done
  • Probably not necessary given the low number of integrations (see Q&A)
• Within a maintenance window
  • export all remaining data from Notifications
    • This is all data if there was no prior export
    • If there was a prior export, this starts from after the last value of the sorted column in the previous export
    • Unnecessary if the job reads from the DB directly
  • Run the job to import all remaining data (starting from last value of the sorted column if there was a previous export / import)
    • This needs to lookup corresponding Default Workspace ID per Org ID
    • This is immutable / permanent, so this can be cached indefinitely if needed
  • Turn on writes to Kessel
    • From this point, writes to Kessel must remain on. If they are turned off, we have to run another migration.
    • This does NOT require reads/access checks to use Kessel–just writes. Those are two separate config/feature flags.

Q&A

• How many integrations are there total in the db?
  • 24223 as of 9/30/24