Index and order - qdb - lcia

[bkuczenski]

index-and-order is not properly part of xdb, that is data management. so that stuff came out.
this thread introduces qdb as a separate router for eventual replacement /supplementation with a remote service

There also needs to be some way to test functionality wrt specific data sources.
WE STILL HAVEN'T DECIDED HOW TO MANAGE DATA SOURCES
this is a problem- but not for xdb

xdb syncs a directory structure- "AWS" is not even relevant. xdb has the content locally and it is ETL [e.g. dagster] to ensure necessary resources are provisioned.

then it runs. the only config is:

• a list of origins
• a k:v set of public keys of trusted signing authorities, to validate JWTs
• this should also be queryable from an auth server
• this is ostensibly working

but nothing is tested.

Testing plan:
I don't know how to test the uvicorn server generally. but assuming it's up, the tests would be:
by route. what does the docs say?
here is a test client:
miguelgrinberg/python-socketio#332 (comment)

or better: https://stackoverflow.com/a/57816608

So, we test xdb locally, but we also need a data test. we have expectations of ecoinvent 3.6 vs 3.7; we have uslci; lists of expected-open resources generally. xdb is the first product and when it's live it's live. but that's a test of an Antelope service, not of xdb.