.... as the order is only relevant intra manifest ...

Sorry that's not true,
my solution MUST also work
over all sourced manifests.
This is a feature not a bug ...

If a user would use the option to not execute
sourced manifests in order, simply unset
the variable bevor sourcing the file.

If the user whish to execute the
sourced manifest also in order (only intra manifest),
he could set the variable after the first type
and unset after the last type.

Setting each type require the bevor type
is the oposite of parallel execution.

I think parallel exectuion is only possible
with manual require settings.

So it would be nice to give the user
the choice to simplyfy the requirements
or to manual tune and execute (in future) in parallel
even on the same host.

Please wait for the next commit,
i have made some improofments.

Greats, Daniel






2014/1/18 Nico Schottelius <notifications@github.com>

> In cdist/emulator.py:
>
> > @@ -71,6 +71,7 @@ def __init__(self, argv, stdin=sys.stdin.buffer, env=os.environ):
> >              raise MissingRequiredEnvironmentVariableError(e.args[0])
> >
> >          self.object_base_path = os.path.join(self.global_path, "object")
> > +        self.typeorder_path = os.path.join(self.global_path, "typeorder")
> >
>
> Something that may not be known outside of docs/dev/logs reading people
> (don't read it, it's a braindump directory!) is that there are ideas to
> parallelise cdist. This could potentially mean that multiple manifests are
> executed at the same time.
>
> A very easy fix for this is to use self.object_source as a base for the
> name/path of self.typeorder_path, as the order is only relevant intra
> manifest (maybe even creating something like
> $__global/typeorder/path/to/manifest when executing any manifest - just an
> idea)
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/telmich/cdist/pull/264/files#r8986767>
> .
>