I have multiple environments and used to work with highstate on them, using
declarative description in top.sls in states and in top.sls in pillar.
Them i tried to move to orchestration system as my states on minions begin
to depend on each other.
When i made an orchestrate sls file and wrote highstates only there and
added some requirements in order to describe my top.sls cross minions
dependencies, i ran into a big problem using orchestrate runner: execution
like salt-run state.orch orchestration.mycluster *uses only base
U can see in develop branch code like this:
def orchestrate(mods, saltenv='base', test=None, exclude=None, pillar=None):
It was a disappointment for me. I really don't understand why do u have to
restrict explicit env specification when running orchestrate, while when
using state.highstate environments and appropriate matches for them could
be declarative described in top.sls.
Is it a bug or my misunderstanding? Please, help.
Also in new rc there is an orchestrate_highstate runner, can u tell, what
is it for? I tried using it, but it failed with exception.
You received this message because you are subscribed to the Google Groups "Salt-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
For more options, visit https://groups.google.com/d/optout.