Uploaded image for project: 'Ansible Strategy'
  1. Ansible Strategy
  2. ANSTRAT-630

Azure Eventgrid Subscription

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Obsolete
    • Icon: Normal Normal
    • None
    • None
    • content
    • False
    • False
    • ANSTRAT-454 - Phase 3: Azure Content Collection Enhancements

      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... Business Impact: 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.

      Story

      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.

            Unassigned Unassigned
            sharwell@redhat.com Scott Harwell
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: