From a5f1348ca3123ddb77558738434706db183039f0 Mon Sep 17 00:00:00 2001 From: Nico Schottelius Date: Sat, 15 Jan 2011 14:47:43 +0100 Subject: [PATCH] more ideas on provider integration Signed-off-by: Nico Schottelius --- doc/internal/provider-integration | 42 ++++++++++++++++++++++++++++++- 1 file changed, 41 insertions(+), 1 deletion(-) diff --git a/doc/internal/provider-integration b/doc/internal/provider-integration index 5b164dd8..2e33a9fc 100644 --- a/doc/internal/provider-integration +++ b/doc/internal/provider-integration @@ -1,2 +1,42 @@ This document is a brainstorming document, -on how to integrate providers. +on how to integrate providers. Providers +had been "type" in previous discussion. + +Proposed/discussed structures: + +1) 2010-11-02 + $basedir/$type/ + properties/ + name/ + required # required | optional + choices # \n liste + + + meta/ + default (shell script) + providers/ + pukman/ + +2) 2010-11-09 + +How to write my own type named "coffee": + + Create the directory /etc/cdist/types/coffee/ + Create the file /etc/cdist/types/coffee/README containing a description of the +type. + If your type supports attributes, create the directory /etc/cdist/types/coffee/ +attributes. + For each attribute, create the file + /etc/cdist/types/coffee/attributes/$attribute_name which contains + + a short description on the first line + then a blank line + then a long description (probably over several lines) + + If you think your type may be useful for others, submit it for inclusion + into cdist at cdist -- at -- l.schottelius.org. + + Create /etc/cdist/types/coffee/init which reads $configinput + (either via cconfig or via environment) and outputs a block of + shell code suitable for running on the client. +