@njuguna-n please review; turns out postgrest doesn't like missing values. I'm not sure how this was working before, maybe it was silently failing? Now it is loudly failing because postgrest returns 400 for these requests, meaning the redis worker doesn't move on and just hangs retrying in the queue.
Also moved initializing the DB to the dbt initialization script. this isn't the right place for it really but there was already some initialization there (creating the schema) so for now just moving it there.
@njuguna-n please review; turns out postgrest doesn't like missing values. I'm not sure how this was working before, maybe it was silently failing? Now it is loudly failing because postgrest returns 400 for these requests, meaning the redis worker doesn't move on and just hangs retrying in the queue.
Also moved initializing the DB to the dbt initialization script. this isn't the right place for it really but there was already some initialization there (creating the schema) so for now just moving it there.