If this should be posted elsewhere, let me know.
I’m looking for real-world stories from organizations that have standardized Ansible automation beyond “a bunch of playbooks in a repo.”
In my current environment, we’re pushing hard toward reusable content (roles, collections, and shared libraries) as the default instead of one-off playbooks. We’re trying to balance a few goals at the same time: keeping the developer experience lightweight, avoiding a “central automation team bottleneck,” and still having enough governance that people trust what’s in the catalog.
I’m particularly interested in how you approached:
•Getting teams to think in reusable components instead of quick scripts (for example: code review practices, templates, linting/policy, training, or “golden role” examples).
•Deciding where content lives and how it’s owned (single monorepo, domain-based repos, or collection-per-team, and how you made ownership and SLAs clear).
•Handling versioning, deprecation, and breaking changes for shared content so that consumers aren’t afraid to depend on the common roles/collections.
•Integrating with Ansible Automation Platform or other tooling to expose an “automation catalog” that people actually use, not just a theoretical library.
If you’ve gone through this journey, what worked, what didn’t, and what you’d absolutely do differently next time?