Background

Customers that rely on Azure Eventgrid for event-driven automation (both internal to other solutions like Ansible) depend on configuring Eventgrid subscriptions with infrastructure-as-code in order to maintain reusable infrastructure configuration code. Support for Eventgrid subscriptions, coupled with examples of how Ansible can be used to automate in event-driven circumstances, will allow Azure customers to expand their automation deployment while leaning into Ansible as the automation engine instead of relying solely on Azure capabilities (with vendor lock-in) or competing automation solutions.

User Stories

As an Ansible on Azure customer I can configure and manage Azure Eventgrid subscriptions through the Azure collection in order to support my development of event-driven automation between Azure's services and Ansible Automation Platform. This will allow me to configure my infrastructure events as code through Ansible Automation and develop Eventgrid subscriptions that can call Ansible APIs to perform other automations when Eventgrid events occur.

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.