On stage, notifications is currently running in hybrid mode, accepting Kafka messages on the platform.notifications.ingress topic with:

• the EAN alone and no OrgId yet
• both the EAN and the OrgId
  If you provide us with an OrgId, then we will use it while processing the Kafka message. Otherwise, we will fall back to the EAN and everything will keep working as usual.
   
  That hybrid mode is however temporary and we will soon start rejecting incoming messages without an OrgId value. So if you haven't migrated the messages you send to us yet, please have a look at our documentation where you can find an example of a Kafka message with the org_id field and please send us both EAN and OrgId by August 19th the latest.
  We will communicate before starting rejecting messages without an OrgId.
   
  Thanks for helping us finalize our OrgId migration as soon as possible!
   
   

• 
  On stage, notifications is currently running in hybrid mode, accepting Kafka messages on the platform.notifications.ingress topic with:

• the EAN alone and no OrgId yet
• both the EAN and the OrgId
  If you provide us with an OrgId, then we will use it while processing the Kafka message. Otherwise, we will fall back to the EAN and everything will keep working as usual.
   
  That hybrid mode is however temporary and we will soon start rejecting incoming messages without an OrgId value. So if you haven't migrated the messages you send to us yet, please have a look at our documentation where you can find an example of a Kafka message with the org_id field and please send us both EAN and OrgId by August 19th the latest.
  We will communicate before starting rejecting messages without an OrgId.
   
  Thanks for helping us finalize our OrgId migration as soon as possible!
   
   

• rhel/edge-management