Change Details

When we add things to the schema, new id is being generated, the problem is that `ksqldb` does not pick up that new field without migrations. We need to run and polish this roll-out process on a `dev` environment and then push to `prod`. **Acceptance criteria** - Image field is accessible through Realtime API - Runbook for the roll-out process created. **ToDo** - [ ] figure out the best way to update schema ID in ksqldDB - [ ] create new migrations and push and test them in `dev` - [ ] create a Runbook - [ ] deploy to production

When we add things to the schema, new id is being generated, the problem is that `ksqldb` does not pick up that new field without migrations. We need to run and polish this roll-out process on a `dev` environment and then push to `prod`. **Acceptance criteria** - Image field is accessible through Realtime API - Runbook for the roll-out process created. **ToDo** - [x] figure out the best way to update schema ID in ksqldDB - [x] create new migrations and push and test them in `dev`

When we add things to the schema, new id is being generated, the problem is that `ksqldb` does not pick up that new field without migrations. We need to run and polish this roll-out process on a `dev` environment and then push to `prod`. **Acceptance criteria** - Image field is accessible through Realtime API - Runbook for the roll-out process created. **ToDo** - [ - [x] figure out the best way to update schema ID in ksqldDB - [ - [x] create new migrations and push and test them in `dev` - [ ] create a Runbook - [ ] deploy to production