Azure image and gallyerimageversion info modules don't support check mode about azure

[Fred-sun]

@jghal Thank you for your interest in ansible_collection_azure. The "check" parameter does not support modules that rely on the results of other commands, so if you want to view resources through the "*_info" module, it is recommended that you drop the "check" parameter.
You can refer to the documentation: https://docs.ansible.com/ansible/latest/user_guide/playbooks_checkmode.html

[jghal]

Thanks @Fred-sun. Is there some reflection going on so that the core Ansible engine knows not to allow check mode within a module, or is it up the module developer to support check mode based on a published policy?

I wanted to use --check --diff to do CI unit testing pipelines on a playbook whose main purpose is destructive (destroying resources). Without having check mode I have to write in extra logic such as a boolean variable used in a when or a tag. I'm essentially just writing my own way to simulate check mode even though the flags to convey this intent is already built into Ansible via check mode.

[Fred-sun]

@jghal I'll try it as you suggest. Until then, can you using the "-- skip-tags" to skip these module check? Thank you very much!

[jghal]

Yes, I can use workarounds to not having check mode. I just would prefer not to have to. I feel like the spirit of check mode is that the target host is not modified, and since there is fundamentally no target host with these modules they should support check mode.

[Fred-sun]

@jghal Thank you for your advice and we will discuss the need for an increase as soon as possible.

[Fred-sun]

@jghal This problem should be turned off, and the check mode mode should be used to manage modules! Thank you very much!