blob: d75160cdf518d1c65ef0000ffd8deed6b23f1c6c (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
|
.. -*- mode: rst -*-
.. _server-plugins-generators-semodules:
=========
SEModules
=========
.. versionadded:: 1.3.0
.. automodule:: Bcfg2.Server.Plugins.SEModules
:no-members:
Usage
=====
To use the SEModules plugin, first do ``mkdir
/var/lib/bcfg2/SEModules``. Add ``SEModules`` to your ``plugins``
line in ``/etc/bcfg2.conf`` and restart bcfg2-server.
The SEModules directory contains modules in a layout similar to the
Cfg plugin: at the top level, SEModules should contain directories
named after the modules you want to install, and each of those
directories can contain a global module, plus any number of group- and
host-specific modules. For instance::
$ ls -F SEModules
foo.pp/ bar.pp/
$ ls SEModules/foo.pp/
foo.pp
foo.pp.G50_server
foo.pp.H_baz.example.com
For more information on this directory layout, see
:ref:`server-plugins-generators-cfg`.
Entries
=======
SEModules handles ``<SEModule>`` entries. For instance:
.. code-block:: xml
<Bundle>
<SEModule name="foo.pp"/>
</Bundle>
The ``.pp`` extension is optional.
.. note::
If you use a ``BoundSEModule`` tag, you must *not* include the
``.pp`` extension. This is not recommended, though.
You can also install a disabled module:
.. code-block:: xml
<SEModule name="foo" disabled="true"/>
|
