Event-Driven Ansible Enhancements in AAP 2.6 — What's New

Introduction

Event-Driven Ansible (EDA) continues to evolve in AAP 2.6 with enhancements that provide greater flexibility and control over event-driven automation workflows. This article covers the key EDA improvements in the 2.6 release.

See also: Enhanced Kafka Integration for Event-Driven Ansible in AAP 2.6

What's New in EDA for AAP 2.6

External Secret Management Support

AAP 2.6 adds support for external secret management systems in EDA, including HashiCorp Vault. This allows you to: • Store sensitive credentials outside of EDA configurations • Rotate secrets without modifying rulebooks • Comply with enterprise security policies • Use existing Vault infrastructure

# Example: Using HashiCorp Vault with EDA
sources:
  - name: webhook_source
    type: ansible.eda.webhook
    args:
      host: 0.0.0.0
      port: 5000
      token: "{{ lookup('hashi_vault', 'secret/eda/webhook_token') }}"

Editable Project URLs

You can now modify project URLs after creation, providing: • Easier project management when repository URLs change • Support for migration between Git hosting providers • Simplified development-to-production workflows

EDA-Triggered Job Labels

A new label identifies jobs that were triggered by Event-Driven Ansible. This makes it easy to: • Distinguish between manually triggered and event-triggered jobs • Track EDA activity in the automation dashboard • Filter and report on event-driven automation separately

Enhanced Kafka Support

Kafka integration receives significant improvements: • Multiple topics — Subscribe to multiple Kafka topics in a single rulebook • Wildcards — Use wildcard patterns for topic matching • Better error handling — Improved connection resilience and retry logic

# Example: Multi-topic Kafka source
sources:
  - name: kafka_events
    type: ansible.eda.kafka
    args:
      host: kafka.example.com
      port: 9092
      topic: "infrastructure.*"  # Wildcard support
      group_id: eda-consumer

Best Practices for EDA in AAP 2.6

Use external secrets — Never hardcode credentials in rulebooks Label your rules — Use descriptive names for easier troubleshooting Monitor with the dashboard — Track EDA-triggered jobs alongside manual ones Test rulebooks thoroughly — Use the development environment before production

See also: Integrating HashiCorp Vault with Event-Driven Ansible in AAP 2.6

Conclusion

The EDA enhancements in AAP 2.6 address real-world enterprise needs around security, scalability, and observability. These improvements make event-driven automation more production-ready than ever.

For more Ansible tutorials and guides, explore the complete article collection on Ansible Pilot.

Related Articles

• Ansible Vault CLI reference