Only very recent zfs on linux supports parsable output for zfs/zpool commands.
Also Oracle ZFS did not implement this at all.
Since we now do value normalization, we can deal with not having parsable output.
The change in #41233 added the "apply_to" kwarg to rabbitmq.set_policy. Since
the arg was not added at the end of the kwarg list, there was an API change.
In addition, when the order of "apply_to" and "priority" was swapped, the
corresponding kwargs were not changed, which causes a stack trace and the
rabbitmq_policy state to fail.
This change fixes#46880 so that the policy option will work correctly and we
can avoid this API change for the module. In 2017.7.x versions of Salt, the
order of args/kwargs is `vhost`, `name`, `pattern`, `definition`, `priority`,
and then `runas`. Therefore, `apply_to` must be last.
Fixes#46880
This removes the changes from #46520 that were merged-forward and not handled
correctly in #46907.
Changes to `salt/utils/schedule.py` cannot be merged forward to develop as the
code there has be significantly refactored. The change in #46520 will need to
be applied directly to `develop` instead.
Since the order of the list in the dict can change, the assertEqual
might fail. assertCountEqual not only checks the count, it also checks
for matching elements regardless of the order. assertCountEqual is
Python=>3.2.
Domain lifecycle event was not using the callback provided event type
for the tag, but rather using the realy event. Harmonize this with the
other callbacks
Use a dictionary to describe all events objects (domain, network, pool,
nodedev and secret). This allows future extensions of the data
describing these objects.
Also make sure to provide the object UUID where one exists since some
client applications use them to identify objects.
Parameters order is different when firing events on master or minion.
The order for master was wrong. Also added documentation on how to setup
polkit to run the engine on a master node.
