Building Scalable Automation with Configuration as Code
Configuration as Code (CaC) provides an approach for managing configurations in the same structured manner as application code, making changes easier to track, reproduce, and automate. Combined with Git and CI/CD principles, it enables organizations to establish version-controlled and automated processes for managing Red Hat Ansible Automation Platform configurations.
Configuration as Code for Enterprise Automation with Red Hat Ansible Automation Platform (AU245) is designed to teach IT professionals how to manage and scale Red Hat Ansible Automation Platform environments by applying the fundamental principles of Configuration as Code.
Throughout the course, participants explore essential practices ranging from managing code and configuration with Git to team collaboration, CI/CD concepts, and automated management of Ansible Automation Platform configurations.
Organizational Impact
Implementing a Configuration as Code methodology helps organizations establish more robust, version-controlled, and automated processes for configuration management.
Managing configurations as code improves the ability to track changes, supports greater consistency across environments, and reduces errors that may result from manual configuration processes.
This approach also helps organizations scale automation more reliably while reducing operational risks and potential downtime associated with manual and error-prone deployment practices.
Individual Impact
AU245 provides participants with a foundation in Git and CI/CD principles that supports the transition from manually administering Red Hat Ansible Automation Platform to a more automated and code-driven management approach.
Participants develop practical skills for beginning to manage configurations as code, including safely validating and testing configuration changes and promoting deployments from staging environments into production.
By applying these fundamental operations practices, participants can improve collaboration across teams, reduce deployment errors, and develop greater confidence when implementing critical system changes.
