I'm not sure why I'm getting this error in the sanity test though.. And only for 3.11

Running sanity test "import" on Python 3.8
Running sanity test "import" on Python 3.9
Running sanity test "import" on Python 3.10
Running sanity test "import" on Python 3.11
ERROR: Found 1 import issue(s) on python 3.11 which need to be resolved:
ERROR: plugins/inventory/azure_kql.py:104:0: traceback: ModuleNotFoundError: No module named 'pandas'

Our test environment did not rely on pandas, so this error did not occur. If an error occurs in python3.11, does it mean that pandas is not included in the python3.11 standard library and needs to be installed by oneself?

Hi,
I was using Graph to generate an inventory and it kept coming up with incorrect output. I notified MSFT of that and they said by design Graph is not a reliable source of information. I would suggest to not use Graph for collection of an inventory.

Greetings
Klaas

For the MSFT people, the support case number was 2406170050002212

I'll quote from it for the red hat people:

"""
For a definition of what ARG should do, I can only refer to the official documents that states “Azure Resource Graph is an Azure service designed to extend Azure Resource Management by providing efficient and performant resource exploration.”
I think the keyword in that sentence is “efficient”. If ARG also performed data validation, it would not be efficient anymore. I quoted an article earlier that mentioned the full scan that ARG is doing to make sure it has all its properties. This scan can take 30 hours to become available due to the amount of data it needs to query. If it also had to validate the data it received, it would take way so much time that the information would be out of date by the time it was made available.

I think the answer to your question “Does Microsoft want to change that?” is “No, we don’t want to change how this works right now”. Andreea discussed the case with both ARG and Compute resource groups. They found the reason for the missing property but due to the design, there is nothing that can be changed without re-architecting some major Azure components and this is not something we’re ready for at this point. Maybe in the future, but for now we’ll have to live with validating the properties on the client side.
"""

In the case I was exploring I noticed that important fields for an inventory (in this case current powerstate) would silently fail and just show "" instead of the actual powerstate. I have since reverted to using the API directly. This, at least from the information in that case, is the only interface on which microsoft provides "guarantees" for information accuracy.

@Klaas- Thanks for bringing this limitation, I can also add one more limitation of ARG: for newly created resources, it will need some time to propagate to ARG until they are queriable.

@p3ck Do you mind to put down some note/warning in the document of this new inventory, about the ARG limitations?

It also goes the other way, just on Friday I had another case with long-deleted resources still showing up in Graph. I stopped monitoring the situation after 8h post-delete because my day was finished. The answer from support is simply "this is a known issue" -- so also in that area, don't rely on Graph. If you want a proper inventory you have to use API until MSFT rethinks what Graph is and what it should guarantee to it's users

@Klaas- Thanks for bringing this limitation, I can also add one more limitation of ARG: for newly created resources, it will need some time to propagate to ARG until they are queriable.

@p3ck Do you mind to put down some note/warning in the document of this new inventory, about the ARG limitations?

I will put something in the notes. I also have an inquiry to the customer who is currently generating their inventory via ARG and if they are aware of this issue.

the official Resource Graph answer is "for new resource it can take up to 30 hours to appear in graph" and same for deleted resources "it can take up to 30 hours until a deleted resource disappears from graph"

I've put a disclaimer in the inventory module.

pipeline test: https://dev.azure.com/azclitools/internal/_build/results?buildId=259862&view=logs&j=b6daf38b-8237-596a-54bf-319fae9744cb&t=4d624bf0-640b-531f-6c03-5be4c6767d72

I've made a fix and some additions to warning in #2002