Put alembic code inside Python package?

[kylebarron]

Would it make sense to put the alembic dir within stac_api as a Python module? Then downstream libraries could have access to that without copying files from the repo.

[geospatial-jeff]

I am a fan of including the alembic migrations with the python module but not a fan of what you are proposing with respect to the current state of the repo.

Currently there is a bunch of postgres related code in this repo (migrations, data models etc.) but that is only because we've been building the API using postgres as the "canonical" backend. In the future, the goal is to have this repo just contain the STAC-compliant API layer and respective base classes, with any backend specific code living somewhere else.

The library is constructed as is (backend code + api layer in same place) for ease of initial development, but we are quickly approaching a point where it is healthier to separate the two because it promotes better separation of concerns (#74 was a big step in this direction), at which point it makes sense to ship the default alembic migration with the backend code.