|
|
|
@ -110,6 +110,7 @@ setup the variable "require" to contain the requirements. Multiple |
|
|
|
|
requirements can be added white space separated. |
|
|
|
|
|
|
|
|
|
-------------------------------------------------------------------------------- |
|
|
|
|
|
|
|
|
|
1 # No dependency |
|
|
|
|
2 __file /etc/cdist-configured |
|
|
|
|
3 |
|
|
|
@ -121,19 +122,18 @@ requirements can be added white space separated. |
|
|
|
|
9 require="__file/etc/cdist-configured __link/tmp/cdist-testfile" \ |
|
|
|
|
10 __file /tmp/cdist-another-testfile |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-------------------------------------------------------------------------------- |
|
|
|
|
|
|
|
|
|
Above the "require" variable is only set for the command that is |
|
|
|
|
immediately following it. Dependencies should allways be declared that way. |
|
|
|
|
|
|
|
|
|
On line 4 you can see that the instantion of a type "__link" object needs |
|
|
|
|
On line 4 you can see that the instantion of a type "\__link" object needs |
|
|
|
|
the object "__file/etc/cdist-configured" to be present, before it can proceed. |
|
|
|
|
|
|
|
|
|
This also means that the "__link" command must make sure, that either |
|
|
|
|
"__file/etc/cdist-configured" allready is present, or, if it's not, it needs |
|
|
|
|
This also means that the "\__link" command must make sure, that either |
|
|
|
|
"\__file/etc/cdist-configured" allready is present, or, if it's not, it needs |
|
|
|
|
to be created. The task of cdist is to make sure, that the dependency will be |
|
|
|
|
resolved appropriately and thus "__file/etc/cdist-configured" be created |
|
|
|
|
resolved appropriately and thus "\__file/etc/cdist-configured" be created |
|
|
|
|
if necessary before "__link" proceeds (or to abort execution with an error). |
|
|
|
|
|
|
|
|
|
All objects that are created in a type manifest are automatically required |
|
|
|
|