On Thu, 6 Jul 2023 at 09:14, Bastian Blank <[email protected]> wrote: > > Hi Luca > > > * New upstream version 20230705+git (Closes: #1040406) > > Could you please describe how a new version of the azure module can fix > that? The dependency needs to be updated as well at least. > > Also, how can it be that azure-cli is updated without the corresponding > azure?
Because the upstream projects are sadly an absolute mess. The mass of code in python-azure (upstream azure-sdk-for-python) is an amorphous blob without any logic or reason, with hundreds of modules that get thrown in the repository incoherently. At any give commit these modules can be incompatible with each other in unpredictable ways, so updating python-azure is like playing russian roulette, so I avoid doing it unless it becomes obviously necessary (as you noticed for the 'az vm' subcommand in the bug you filed). And to top it all, upstream azure-cli just bumps its requirements.txt on every release to whatever is available on the developer's machine that day, so it is completely unreliable and needs to be ignored. Yes I will bump the dependency in the next azcli upload, but I wanted to push the fix immediately. Honestly, if I didn't need this for $work, I'd have filed an RM bug long ago. But the upstream 'releases' are even worse and vendor everything including the full python interpreter and openssl, without any security maintenance guarantees, so I don't want to have to rely on them. Kind regards, Luca Boccassi
