Plugins

Plugins are the source of all logic used in building a config. They can perform one of several tasks:

1. Generating configuration inventory lists for clients
2. Generating configuration entry contents for clients
3. Probing client-side state (like hardware inventory, etc) – the generic client probing mechanism is described at Probes.
4. Automating administrative tasks (e.g. SSHbase which automates ssh key management)
5. Generating client per-entry installation decision-lists

Enabling Plugins

In order for the Bcfg2 server to use a plugin, it needs to be listed on the plugins line in bcfg2.conf.

Default Plugins

The Bcfg2 repository contains the all plugins currently distributed with Bcfg2.

Metadata (Grouping)

• GroupPatterns
• Ldap
• Metadata

Each of these plugins has a corresponding subdirectory with the same name in the Bcfg2 repository.

Abstract Configuration (Structures)

• Bundler
• altsrc
• Defaults
• Deps

Each of these plugins has a corresponding subdirectory with the same name in the Bcfg2 repository.

Literal Configuration (Generators)

• Cfg
• Decisions
• NagiosGen
• Packages
• Pkgmgr
• Rules
• SEModules
• SSHbase

Each of these plugins has a corresponding subdirectory with the same name in the Bcfg2 repository.

Connector Plugins

• AWSTags
• GroupLogic
• Properties
• PuppetENC
• TemplateHelper

Statistics Plugins

• Reporting

Reporting can be enabled by adding it to the plugins line in /etc/bcfg2.conf.

Version Plugins

• Bzr
• CVS
• Darcs
• Fossil
• Git
• Mercurial (Hg)
• Svn

Miscellaneous Plugins

• ACL
• Guppy
• Trigger

Plugin Roles (in 1.0)

In version 1.0, plugins have been refactored into a series of roles. This are fine-grained plugin capabilities that govern how the server core interacts with plugins.

More details can be found in Plugin Roles