How to arrange private packages for use on ADX
Regarding using external artifacts in the python plugin in Azure Data Explorer
The documentation includes these two related notes about private python packages and wheels:
- For private packages, zip the folder of the package and the folders of its dependencies.
- Make sure to zip the
.whlfiles themselves, and not their parent folder
My question is, what does this look like in practice? Say that I have the following private python package:
my_private_pkg.whl
and it requires the following python packages not available in the ADX python plugin:
python_package_not_avail_on_ADX_1.whl
python_package_not_avail_on_ADX_2.whl
How should this all be organized and uploaded to my storage container? I've managed to have some success, but it seems like my approach is hacked together, and likely not the most efficient way.
Andrea