if first type in initial manifest doesn't have CDIST_ORDER_DEPENDENCY, then it works:
$ for f in manifest/bug type/__foo/manifest type/__bar/manifest type/__baz/manifest; do echo; while read -r…
@ander CDIST_ORDER_DEPENDENCY instructs cdist to record last created type as a requirement for current processed type, from type creation order list.
For the first example above, this is what…
@steven @nico What if we try to change how CDIST_ORDER_DEPENDENCY works?
How about defining context in which this env var is valid, and a local list of type creation order start from beginning in…
CDIST_ORDER_DEPENDENCYis evil, it breaks things.
yes, but it is necessary evil. i, for one, support this evil env var.
CDIST_ORDER_DEPENDENCY should only be valid within the manifest where it is used. That we have a global file tracking this is at least one of the problems.
What if we have a 'type_creation_order'…
@steven Yes, that is in the idea I am talking about. I will experiment with it.
we have "stdin inside a loop" issue here if i use while read.
so, __file foo < /dev/null or # shellcheck disable=SC2013 ?
@ander I wouldn't ignore and disable this. What if file contains spaces? Current loop wouldn't work.
cdist does not support file names containing space. It would also break require="" variable. Through all the levels of shell and writing to files and reading from files it would be complicated.
So,…