A recent PR by @f-necas adds the datafeeder compo into this repo. I believe it might be improved a bit.
For instance, a bit of documentation about what the PR does, adds, implies in term of configuration might help. This is not, IMO, a light and straightforward addition.
But this is not the main topic of this ticket: I see in the datafeeder compo file the addition of a new DB for airflow: docker-compose.datafeeder.yml
I got the impression that this is an applicative DB, for airflow internal storage. If this is the case, the standard geOrchestra pattern would be to use a schema in the geOrchestra applicative DB. That would give a cleaner integration. And avoid having tons of postgres containers
A recent PR by @f-necas adds the datafeeder compo into this repo. I believe it might be improved a bit.
For instance, a bit of documentation about what the PR does, adds, implies in term of configuration might help. This is not, IMO, a light and straightforward addition.
But this is not the main topic of this ticket: I see in the datafeeder compo file the addition of a new DB for airflow: docker-compose.datafeeder.yml
I got the impression that this is an applicative DB, for airflow internal storage. If this is the case, the standard geOrchestra pattern would be to use a schema in the geOrchestra applicative DB. That would give a cleaner integration. And avoid having tons of postgres containers