Hi there
We have an internal PyPI index to which we deploy private packages that we'd then like to pip install
into our Python Azure function. Because our packaging index is not reachable from the Azure cloud we've so far opted for --build local
. However, this has turned out to be a bit fragile as a couple of times now after adding new dependencies we get errors like these:
There was an error restoring dependencies. ERROR: cannot install pyrsistent-0.16.0 dependency: binary dependencies without wheels are not supported when building locally. Use the "--build remote" option to build dependencies on the Azure Functions build server, or "--build-native-deps" option to automatically build and configure the dependencies using a Docker container. More information at https://aka.ms/func-python-publish
I'd rather not get into the --build-native-deps
option if I can avoid it as the CI runners we're using aren't under our control and I don't know how straight-forward it would be to have them configured for --build-native-deps
.
Hence I was wondering whether it isn't possible to first pip install
our couple private packages on our CI runner into a magic folder and have that folder uploaded to Azure to be considered in an otherwise standard remote build - or something along those lines.
Thanks,
Damian