Background

Support for VM and disk image fact details would allow for playbook idempotence as automators build out support for their automations based on what VMs are deployed within a cloud region as opposed to being configured within a playbook. Per the supplied customer example, the CLI is used to request image data and retrieve the necessary image in order to create a VM or perform a later operation. Support for AMI facts would allow this operation to be native to Ansible and a better automation experience for our customers.

The equivalent of az vm list and az vm disk operations to collect facts for a given az region would simplify automations that require this capability.

User Stories

As an Ansible on Clouds user I can get information / facts from Azure APIs about the state of my Azure Virtual Machines and disk images so that I can construct decision-driven automations with Ansible based on the current state of these Azure resources.

Supporting documentation

<include links to technical docs, diagrams, etc>

Ready-Ready

https://docs.google.com/document/d/1dBW492UfCR5JxUvcx6efjYP_ibCdiwGONS-sxDb_SPU/edit# 

Complete Ready-Ready checklist

Definition of Done

Should be agreed upon per team; add/remove/update to reflect:{}

• CI is running, tests are automated and merged and successful
• DEV upstream code & tests merged
• DEV upstream documentation merged
• DEV downstream build attached to advisory
• QE - Test plans documented and attached to epic (or link to source)
• QE - automated tests merged and passing
• Docs - Downstream documentation is merged
• PM - all acceptance criteria are met (note: we want to start using the AC specific field, but please fill out below in the meantime)

Note: please also fill out the 'Acceptance Criteria' to indicate functional criteria aka scope, specific to this issue, that should be met in order to 'accept' the work to consider complete.