This should be an easy one, but I'm straight-up brain mush this month.

alembic

is packaged into my pex file, and I want to run the command line to test out migrations and whatnot, but that's looking for an

alembic.ini

file. Since I can't bundle

files

into a

pex-binary

, I need to use a

resource

. However, when I do that,

alembic

CLI doesn't know where to look for the config. I think it ends up getting packaged into site packages or something. Anyone have experience with this? Eventually I'll be bundling the command into a

scie

with the rest of my application as a separate command, but trying to quickly test something on a pex

if you run the pex with a known path, you could perhaps point alembic to the ini file, knowing where it’ll end up?

Yeah, that might work - I can try that out. For the moment, I just bundled it in the SCIE, and it seems to be working? I'll know momentarily

The "quick" hack we use for this is to have a wrapper for the alembic CLI, that first unpacks the config to a temporary directory, then

os.chdir

to that directory, and then invokes

alembic.config.main(argv=args)

.

Ah, okay, that's interesting. You can now, with

-c CONFIG_PATH

or using I believe

ALEMBIC_CONFIG

envvar

Here's a wrapper script for Alembic that I use in my own repo: https://pantsbuild.slack.com/archives/C046T6T9U/p1689009675231669?thread_ts=1689006191.431389&channel=C046T6T9U&message_ts=1689009675.231669

Thanks! I'll try it out!