| 1 |
1. Manifests need type explorers to be run before |
| 2 |
Only this way the manifest can use the values |
| 3 |
|
| 4 |
2. Type explorers can depend on the (successful) execution of other objects |
| 5 |
A type explorer may lookup values (ownership, size, processes, etc.) |
| 6 |
that are depending on the code of other objects. |
| 7 |
|
| 8 |
3. The 'require="a" b' dependency specifies only that execution of b needs to wait until a is finished |
| 9 |
Other requirements given at another position may not be |
| 10 |
executed before b, as cdist interprets require="a" as |
| 11 |
"a is everything that is needed to realise b" |
| 12 |
|
| 13 |
4. The 'require' state is thus *not* suitable to trigger reloads |
| 14 |
A type b, which uses the require="" statement to wait for all |
| 15 |
require="" dependencies, may be executed in an incomplete |
| 16 |
status. |
| 17 |
|
| 18 |
5. Depending on multiple dependencies defined at different locations requires all objects to be present |
| 19 |
Because otherwise the dependent object cannot be sure that the |
| 20 |
list of objects it waits for is complete. |
| 21 |
|
| 22 |
6. If a statement requires all objects to be present, all manifests must have run already. |
| 23 |
If all manifests have run already, also all type explorers have run already (#1). |
| 24 |
If all type explorers have run already, some objects may have been finished completly already (#2). |
| 25 |
|
| 26 |
7. Because of #4 and #6, we need to introduce another dependency that allows reloading after |
| 27 |
|
| 28 |
8. Because the object could be finished already due to a 'require' dependency, we need another script |
| 29 |
Maybe "gen-post-run-local", "gen-post-run-remote" |