Creating a seperate python client for clusto-apiserver
would have multiple codebases that required updating, namely schema and drivers.
We add support for http(s) DSNs that will query an apiserver instance instead of using sqlalchemy.
These will probably all be PRs so that this will be more managable.
- Modify usage of
SESSION
to only be functional whenSESSION
is instantiated. - Implement the ability to recognize
http
DSNs and raiseNotImplementedError
for any method that requires queries. - Move object serialization methods from
clusto-apiserver
to core. - Implement core get methods.
- Implement all other methods.
At first I thought it would be a good idea to try and have all of these methods reference a utility that would decide between querying the api or the db, but there were few enough methods and unique enough queries that it simply would not save any reproduced code.
This sounds reasonable to me. 👍