This function is old code that is unneeded due to changes in how salt
manages packages. It also represents a bug in which trying to use a
pkg.removed state using the pkgname:i386 format used by apt for 32-bit
packages on 64-bit systems always fails, because the package is
identified as pkgname, not pkgname:i386. Additionally, using just
"pkgname" in your pkg.removed state would fail, because running "apt-get
remove pkgname" would fail for pkgname:i386.
This commit refreshes modules when there are changes in a file.symlink
state with 'bin' in the name. Making this distinction keeps refreshes
from being done for all symlinks, reducing the amount of overhead this
change would introduce. A symlink with 'bin' in the name is likely to
change the available commands on the minion, and thus might make
available certain states/modules which rely on the existence of a given
command in the user's PATH. Without a refresh, these states/module
function calls would fail despite the needed shell command technically
being available.
Salt dynamically reloads modules durring highstate calls to ensure that
the highstate does not need to be run twice. If this behavior is not
being seen then this is a bug of the highstate run is not tracking the
software insalation of powerpath correctly and needs to be extended
Now that rh_service.py has been refactored in such a way that chkconfig
is needed less, module context is not used. Therefore, the logic that
clears out this variable is now unnecessary.
Since the function doesn't really return an empty password, but rather
the default hash, this change makes the naming more accurate, especially
since this function is exposed to the user.
chkconfig uses comments at the top of the initscript to decide which
runlevel to enable/disable the service. Don't disable by default, as it
stomps on normal chkconfig behavior.
This commit cleans up some unused arguments in user and group
management, storing them in **kwargs. Warnings are logged when the
arguments are used. Fixes#6070.
This makes the field name consistent with the other shadow modules. Note
that the passwd field is not used at all in Windows user management, so
this is merely a cosmetic change.
The passwd field in the output from shadow.info was normalized in
508d816 and 6239136 to make it easier for states to manage users, but
this prevents users from setting the password to the default password
hash. This commit fixes that regression.
