Structuring Ansible Projects
Guide to starting and organizing Ansible projects, from basic inventory setups to advanced collections and execution environments.
Guide to starting and organizing Ansible projects, from basic inventory setups to advanced collections and execution environments.
Guideline for securely accessing Ansible Vault during development without storing passwords in plain files, using environment variables and scripts.
Best practices for utilizing dictionary merging in C2 Ansible inventory projects.
Docker-in-Docker (DinD) is a common technique used in GitLab CI/CD pipelines on Kubernetes to run Docker commands within Docker containers.
Ansible engineering and operations should be treated as distinct disciplines to promote high-quality, maintainable automation. This separation ensures that engineering focuses on building scalable, reusable code, while operations handles deployment, monitoring, and day-to-day execution.
Use a group-based approach to organize your Ansible inventory and variables for different environments.
Automate Red Hat Enterprise Linux (RHEL) registration and subscription in C2 Platform development environments using Vagrant for seamless access to Red Hat resources.
When targeting MS Windows hosts, use slashes for all paths. Convert to backslashes only if necessary.
In Scrum-based Ansible projects, story points and velocity should be estimated and measured accurately, with a strong emphasis on the business value derived from automation content. Story points aren’t about time but about relative effort, complexity, and risk.
Guidance on managing secrets using Ansible Vault in Ansible projects, with a focus on Ansible Automation Platform (AAP) and AWX.
Adopt consistent and meaningful naming for sprints, inspired by Semantic Versioning (SemVer) principles. This “SemSprint” approach makes sprint names descriptive, improving communication and traceability.
Learn how to effortlessly synchronize a folder from your host machine to the guest machine.
Prefix variable names with role or project prefix.
Guidelines and examples on how to make Ansible flexible and easy to use.
Establish effective Definition of Done (DoD) criteria specifically for Ansible projects to ensure that deliverables are complete, tested, and ready for production. DoD acts as a checklist to prevent “done” from meaning “mostly done.”
Ansible configuration that should be local and ignored by Git.
Implement a structured tagging system in Ansible playbooks to increase task flexibility, enhance maintainability, and improve reusability, thus optimizing both development and operational efficiency.
Guidelines for implementing branching and merging policies in GitOps pipelines for Ansible inventory projects to promote changes across environments.
Automate setup of the development environment with multiple Git repositories.
Guideline for using GitLab Runner as an Ansible control node when Ansible Automation Platform (AAP) is unavailable.
Naming with the least amount of keystrokes.
This guideline is tailored for teams that are relatively new to Ansible and wish to gain experience by using internal roles.