Currently the example top file under "Matching Grains in the Top File" has
node_type grains whose values do not match the names of the states which
they specify. (e.g. the `webserver` node_type specifies the `web` state).
Later these values are templated using jinja templates as if they are identical.
This commit adjusts the values in the example to be identical, so that the
template example follows naturally.
* Added support for the agentv2
* Updated os field to match the SD API requirement
* filename is an absolute path on official installations
* Install script URL uses a redirect now, so we should instruct curl to follow them
* Added a missing import
* Updated the settings for the v2 agent
* Fixed pep8 issues
* select v2 agent for the test
This adds an explanation of the python-cffi dep added in pygit2 0.21.0,
and recommends 0.20.3 for LTS distros. It also links to the salt-pack
issue which tracks the progress of adding pygit2 to our Debian and
Ubuntu repositories.
* Revert "Verify auth in saltnado run (#32552)"
This reverts commit b19c5a5ce7.
* Call runner.cmd_async instead to enforce eauth
* Check for both token or user/pass before giving to Salt
* Remove comment as we're now enforcing auth here
* Lint and functionality fix courtesy of Mike P.
* Don't fail the whole request if there's an eauth problem
While it sounds a good idea to check wether the venv_bin exists or not, due to
the implementation of salt.utils.which it fails if the command contains
arguments, for example "/usr/local/bin/python3.4 -m venv":
2016-04-20 12:56:46,564 [salt.state
][ERROR ][45709] An exception occurred in this state: Traceback (most recent
call last):
File "/usr/local/lib/python2.7/site-packages/salt/state.py", line 1594, in
call
**cdata['kwargs'])
File "/usr/local/lib/python2.7/site-packages/salt/loader.py", line 1491, in
wrapper
return f(*args, **kwargs)
File "/usr/local/lib/python2.7/site-packages/salt/states/virtualenv_mod.py",
line 169, in managed
use_vt=use_vt,
File "/usr/local/lib/python2.7/site-packages/salt/modules/virtualenv_mod.py",
line 117, in create
salt.utils.check_or_die(venv_bin)
File "/usr/local/lib/python2.7/site-packages/salt/utils/__init__.py", line
804, in check_or_die
raise CommandNotFoundError(command)
CommandNotFoundError: /usr/local/bin/python3.4 -m venv
Related: #29537
The error message for a bad handshake due to a private certificate has
changed slightly (uppercase/lowercase). This additional if statement
fixes the issues and allows connectivity with a self-signed certificate.
As described in #32753 archived.extracted chnages more permissions that they
should. Since if_missing is None, name is assigned to this variable, this
chnage will help not updating files/dirs permissions outside the actual extracted file.
* Properly handle minion failback failure.
Initiate minion restart if all masters down on __master_disconnect like
minion does on the initial master connect on start.
* Fixed unit test
The Random module can lead to non alpha numeric characters in the
password. Since we also use this for creating the salt, some devices
cannot have these extra characters in their salts, so allow to turn this
feature off as needed.
* Add note about Pillar data cache requirement for Pillar targeting method
* Add `saltutil.refresh_pillar` function to the scheduled Minion jobs
* Minor fixes in docs
* Add note about relations between `pillar_cache` option and Pillar Targeting
to Master config comments with small reformatting
* Document Pillar Cache Options for Salt Master
* Document Minions Targeting with Mine
* Remove `saltutil.refresh_pillar` scheduled persistent job
* Support remote sources in a source list
This commit modifies the source_list check so that remote sources
(http(s), ftp, etc.) are not fetched more than once. To do so, it
adds the use of ``__context__`` in ``cp.cache_file`` and
``file.source_list`` to prevent multiple fetches of a single file in the
same salt run.
* Update tests
Added __context__ to test cases to reflect usage of __context__, and
also added file.source_list to mocked funcs for archive.extracted unit
test.
Thanks to #31598, all matchers are supported for eauth configuration.
But we still have no way to use compound matchers in eauth configuration.
Update the documentation to explicitly express this limitation.
