Roles vs Collections on Galaxy

A role packages tasks, handlers, templates, and default variables for one job, like setting up nginx or PostgreSQL, into a reusable unit.

A collection is bigger: it can ship many roles, modules, and plugins together under one versioned, distributable package.

Since Ansible 2.10, even core modules ship inside collections. They are now the primary way content is packaged and distributed.

Collections use a namespace.collection name like community.general, while a standalone role is named author.rolename.

Installed roles land in your roles path, while collections install into a collections path. Both keep your project tidy.

You fetch content with ansible-galaxy: use the role subcommand for roles and the collection subcommand for collections.

Galaxy shows download counts and a community score. Prefer well-used content and always skim the source before trusting a role on your servers.

The huge community.general collection bundles with many installs, but Galaxy is where you reach for anything beyond that baseline.

Need one focused job? Grab a role. Need a whole toolkit of modules and plugins for a platform? Grab a collection.

Galaxy shares community automation: roles bundle one job, collections bundle many. Pull either with ansible-galaxy and vet it first. 🌌