Avoids the following error when running `salt-call` on OpenBSD:
[ERROR ] Command '/usr/sbin/rcctl get zfs-fuse' failed with return code: 2
[ERROR ] output: rcctl: service zfs-fuse does not exist
This allows for the runner to clear the git lock if any of the
per-remote-only params was present in the configuration.
This also adds PER_REMOTE_ONLY attributes to the winrepo runner and
git_pillar external pillar, and fixes all refs to GitBase's init_remotes
function to include PER_REMOTE_ONLY arguments. This will insulate us
against future headaches if either git_pillar or winrepo gain extra
per-remote-only params, as we will only need to make the change to the
attribute in their respective modules.
Fixes#43650
The merge-forward process needs a more prominent position and explanation
in the contributing documentation. This change attempts to explain this
process a little more fully and incorporates some changes to how we are
handling "main" release branches, "dot" release branches, and "develop"
in a more complete context with merge-forwards.
The addition of checking for the `auth_list` in PR #43467 requires
that the mocked return of `get_auth_list` actually contains something
in the list. These mock calls need to be updated so we can check
for the SaltInvocationErrors.
Support for Linux and Windows platforms to display both the
iSCSI IQN and Fibre Channel HBA WWPNs.
With the integration of storage modules to allow configuration
of 3rd party external storage arrays, these values are needed to
enable the full auotmation of storage provisioning to minions.
Support for Windows, Linux and AIX (iSCSI only)
This is a follow up of this PR: https://github.com/saltstack/salt/pull/43235
With the fix in PR 43235, we are polling the status of the deletion via
show_deployment. This is now also reflected in the tests with this change.
