From 71c679e1a0105490bd5845a15de5e8f1a32e2166 Mon Sep 17 00:00:00 2001 From: "Chris St. Pierre" Date: Tue, 11 Sep 2012 10:32:30 -0400 Subject: Cfg: documented all Cfg modules, added development docs --- doc/development/plugins.txt | 14 ++++++++++++++ 1 file changed, 14 insertions(+) (limited to 'doc/development/plugins.txt') diff --git a/doc/development/plugins.txt b/doc/development/plugins.txt index 59582e255..183126053 100644 --- a/doc/development/plugins.txt +++ b/doc/development/plugins.txt @@ -11,6 +11,18 @@ to implement configuration interfaces and representation tailored to problems encountered by a particular site. This chapter describes what plugins are good for, what they can do, and how to implement them. +Several plugins themselves have pluggable backends, and for narrow +cases you may want to develop a backend for an existing plugin rather +than an entirely new plugin. See the following pages for more +information: + +.. toctree:: + :maxdepth: 1 + + cfg + packages + + Bcfg2 Plugins ------------- @@ -41,6 +53,8 @@ Plugin ^^^^^^ .. autoclass:: Bcfg2.Server.Plugin.base.Plugin + :members: name, __author__, experimental, deprecated, conflicts, + sort_order, __rmi__, init_repo, shutdown :inherited-members: :show-inheritance: -- cgit v1.2.3-1-g7c22