Ah no worries already found the solution :grimacin...
# generali
incalculable-intern-62551
05/18/2023, 9:39 AMAh no worries already found the solution 😬
🎉 2
👏 1
b
broad-processor-92400
05/18/2023, 10:51 AMWhat’s the solution? In case someone else has a similar issue (https://xkcd.com/979/ 😄 )
i
incalculable-intern-62551
05/18/2023, 11:39 AMhttps://pantsbuild.slack.com/archives/C046T6T9U/p1648910404798779. In this channel 😄
incalculable-intern-62551
05/18/2023, 11:58 AMI realised that I could just build another pex solely for running the alembic. Then every time I need to run a new migration, I can just spin up a temporary k8s pod that runs the alembic migration. Feels fine to me because that also means I don't need to package the alembic artifacts into the actual binary
👍 1
e
enough-analyst-54434
05/18/2023, 12:50 PMI will note that thread's feature request is now implemented in Pex with support in Pants 2.16+ (https://www.pantsbuild.org/v2.16/docs/reference-pex_binary#codeargscode) but, IIUC, you just needed `PEX_SCRIPT=foo ./my.pex foo-args`: https://pex.readthedocs.io/en/v2.1.137/api/vars.html#PEX_SCRIPT