Lines Matching refs:pillarenv

191     Yes, this is ``{{ saltenv }}``, and not ``{{ pillarenv }}``. The reason for
398 The :conf_minion:`pillarenv` minion config option can be used to force the
408     pillarenv: base
412 the ``pillarenv`` CLI argument can be used to override the minion's
413 :conf_minion:`pillarenv` config value:
417     salt '*' state.apply mystates pillarenv=testing
423     When running states, the ``pillarenv`` CLI option does not require a
424     :conf_minion:`pillarenv` option to be set in the minion config file. When
425     :conf_minion:`pillarenv` is left unset, as mentioned above all configured
426     environments will be combined. Running states with ``pillarenv=testing`` in
430 Starting in the 2017.7.0 release, it is possible to pin the pillarenv to the
433 when running states, the ``pillarenv`` will be the same. This essentially makes
439     salt '*' state.apply mystates saltenv=dev pillarenv=dev
441 However, if a pillarenv is specified, it will override this behavior. So, the
447     salt '*' state.apply mystates saltenv=dev pillarenv=qa
449 So, if a ``pillarenv`` is set in the minion config file,
451 ``pillarenv`` on the CLI will temporarily override