Investigate possibility of moving all intent data to Postgres #1024
Description
AS A trainer
I WANT to have a single source of truth about intent data
SO THAT possible errors and inconsistencies
Notes
Currently, intent data is stored in both Postgres and OpenSearch. This is not optimal: there is no single source of truth and this is error-prone. This has already led to hard-to-debug issues before, e.g. #705. We see no immediate benefit in continuing to use OpenSearch and would like to move all intent data to Postgres only.
Unfortunately, this might be quite tricky, given that Training module is already live with several clients. This means that we need to create some migration mechanism (some script?) to move intent data — probably examples, maybe something more — from YAML files to Postgres.
Acceptance Criteria
- All data on intents is stored in Postgres and not OpenSearch.
- Migration mechanism for client intent data is created and tested.