Fix dynamic VM fetch failure when I(batch_fetch=true)

[Fred-sun]

SUMMARY

Fix dynamic VM fetch failure when I(batch_fetch=true), fixes #1328

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

azure_rm.py

ADDITIONAL INFORMATION

[TiTi]

Damn this is still not in https://pypi.org/project/ansible/#files (currently 9.4.0)

[Fred-sun]

@TiTi What version of aze.azcollection did you install, and the new changes are released in the version that incorporates this PR. Thank you!

[TiTi]

I had an azure inventory failure for a very specific resource group (using include_vm_resource_groups).
Other resource group in the same subscription was ok (loading fine), but this resource group had more resources (50+ vms) and was unable to list the vms, with a weird json error in -vvvv, which led me to this fix after troubleshooting manually with batch_fetch and az rest.

I had the azure.azcollection which is included in the "ansible" latest pip package (currently 9.4.0).
@Fred-sun Currently, the ansible 9.4.0 package includes azure.azcollection v1.19.0

Manually installing latest azure.azcollection (2.3.0) [with ansible-galaxy collection install azure.azcollection] + requirements (cf docs) added this fix and thus resolved my issue : inventory loaded properly with default batch_fetch=true

I'm surprised this fix from end of november hasn't got to latest "ansible" pip package that's all.

[Fred-sun]

@TiTi azure.azcollection is a part of ansible collection, which is managed through ansible-galaxy. You can only install ansible with pip and then install azure.azcollection with ansible tool ansible-galaxy. Thank you!

[TiTi]

That's incorrect @Fred-sun
Once you install ansible with pip, you get a lot of collections included.
See my link before and this capture :

This actually represents the biggest part of the tarball file.

One can also think those are 'compatible' collections with selected ansible version.

ansible-galaxy is certainly the way to go. But then, why (outdated) collections are pre-installed in the 'ansible' pip module?