2011-02-26 19:41:33 +00:00
|
|
|
cdist-manifest(7)
|
|
|
|
=================
|
|
|
|
Nico Schottelius <nico-cdist--@--schottelius.org>
|
|
|
|
|
|
|
|
|
|
|
|
NAME
|
|
|
|
----
|
|
|
|
cdist-manifest - Define types to be used
|
|
|
|
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
-----------
|
|
|
|
Manifests exist to define which configurations should be applied to a specific
|
|
|
|
host as well as to define which configurations should be applied within a
|
|
|
|
type. Manifests are executed locally and the resulting objects are stored in
|
|
|
|
an internal database.
|
|
|
|
|
2011-03-24 12:27:22 +00:00
|
|
|
The same object can be redefined in multiple different manifests as long as
|
|
|
|
the parameters are exactly the same.
|
2011-03-23 16:16:43 +00:00
|
|
|
|
2011-02-26 19:41:33 +00:00
|
|
|
In general, manifests are used to define which types are used depending
|
2011-03-23 16:16:43 +00:00
|
|
|
on given conditions.
|
|
|
|
|
2011-02-26 19:41:33 +00:00
|
|
|
|
|
|
|
EXAMPLE
|
|
|
|
-------
|
|
|
|
The initial manifest may for instance contain the following code:
|
|
|
|
|
|
|
|
--------------------------------------------------------------------------------
|
|
|
|
# Always create this file, so other sysadmins know cdist is used.
|
|
|
|
__file /etc/cdist-configured --type file
|
|
|
|
|
|
|
|
case "$__target_host" in
|
|
|
|
my.server.name)
|
|
|
|
__file /root/bin/ --type directory
|
|
|
|
__file /etc/issue.net --type file --source "$__manifest/issue.net
|
|
|
|
;;
|
|
|
|
esac
|
|
|
|
--------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
The manifest of the type "nologin" may look like this:
|
|
|
|
|
|
|
|
--------------------------------------------------------------------------------
|
|
|
|
__file /etc/nologin --type file --source "$__type/files/default.nologin"
|
|
|
|
--------------------------------------------------------------------------------
|
|
|
|
|
2011-03-18 01:01:37 +00:00
|
|
|
DEPENDENCIES
|
|
|
|
------------
|
|
|
|
If you want to describe that something requires something else, just
|
|
|
|
setup the variable "require" to contain the requirements. Multiple
|
|
|
|
requirements can be added white space seperated.
|
|
|
|
|
|
|
|
|
|
|
|
--------------------------------------------------------------------------------
|
|
|
|
# No dependency
|
|
|
|
__file /etc/cdist-configured
|
|
|
|
|
|
|
|
# Require above object
|
|
|
|
require="__file/etc/cdist-configured" __link /tmp/cdist-testfile \
|
|
|
|
--source /etc/cdist-configured --type symbolic
|
|
|
|
|
|
|
|
# Require two objects
|
|
|
|
require="__file/etc/cdist-configured __link/tmp/cdist-testfile" \
|
|
|
|
__file /tmp/cdist-another-testfile
|
|
|
|
|
|
|
|
|
|
|
|
--------------------------------------------------------------------------------
|
|
|
|
|
2011-02-26 19:41:33 +00:00
|
|
|
|
|
|
|
SEE ALSO
|
|
|
|
--------
|
2011-03-09 20:54:13 +00:00
|
|
|
- cdist-manifest-run(1)
|
|
|
|
- cdist-manifest-run-all(1)
|
|
|
|
- cdist-manifest-run-init(1)
|
|
|
|
- cdist-type(7)
|
2011-02-26 19:41:33 +00:00
|
|
|
|
|
|
|
|
|
|
|
COPYING
|
|
|
|
-------
|
|
|
|
Copyright \(C) 2010-2011 Nico Schottelius. Free use of this software is
|
|
|
|
granted under the terms of the GNU General Public License version 3 (GPLv3).
|