Plugin Interface

DNF plugin can be any Python class fulfilling the following criteria:

  1. it derives from dnf.Plugin,
  2. it is made available in a Python module stored in one of the Conf.pluginpath,
  3. provides its own name and __init__().

When DNF CLI runs it loads the plugins found in the paths during the CLI’s initialization.

class dnf.Plugin

The base class all DNF plugins must derive from.

name

Plugin must set this class variable to a string identifying the plugin. The string can only contain alphanumeric characters and underscores.

static read_config(conf)

Read plugin’s configuration into a ConfigParser compatible instance. conf is a Conf instance used to look up the plugin configuration directory.

__init__(base, cli)

Plugin must override this. Called immediately after all the plugins are loaded. base is an instance of dnf.Base. cli is an instance of dnf.cli.Cli but can also be None in case DNF is running without a CLI (e.g. from an extension).

config()

Plugin can override this. This hook is called immediately after the CLI/extension is finished configuring DNF. The plugin can use this to tweak the global configuration or the repository configuration.

resolved()

Plugin can override this. This hook is called immediately after the CLI has finished resolving a transaction. The plugin can use this to inspect the resolved but not yet executed Base.transaction.

sack()

Plugin can override this. This hook is called immediately after Base.sack is initialized with data from all the enabled repos.

transaction()

Plugin can override this. This hook is called immediately after a successful transaction.

You may want to see the comparison with yum plugin hook API.