Trying to assert that an exception was raised using
helper_open.write.assertRaises() is bogus--there is no such method. Use
standard unittest.assertRaises() instead.
Trying to assert that an exception was raised using
helper_open.write.assertRaises() is bogus--there is no such method. Use
standard unittest.assertRaises() instead.
These tests have never run automatically because of an incorrect file name.
Added a skipIf on these tests as they are currently non-functioning and the
module they're testing has been deprecated.
Trying to assert that an exception was raised using
helper_open.write.assertRaises() is bogus--there is no such method. Use
standard unittest.assertRaises() instead.
This regressed here: 82a70e015f
The above incorrect assumed that all data flowing into the highstate outputter is expected to be a dictionary. However, looking at _format_host() shows that it does expect to receive multiple types and does handle them accordingly.
I believe that the issue reported in #33915 may be fixed by #35559 instead. This should allow the highstate outputter to display all results instead of stopping after the first one. I would like @terminalmage and @mattglv and possibly @Ch3ll to please confirm this before we get this in.
Resolves#35423
* Comment all lines in the minion config file
* Add unit tests to check for all files in conf/ to be commented out
* Make sure cont/cloud.profiles file is commented out
Matches the cloud.providers file format and other sample config files.
* Add unit tests for sample files in cloud.profiles.d, cloud.providers.d,
and cloud.maps.d
* Make sure all sample config files in cloud.maps.d are commented out
* Make sure all sample config files in cloud.profiles.d are commented out
With the addition of runas for Windows in 2016.3.0, commands run using
Windows runas would not be logged at all, as we would return from the
_run() function before we got to the line where this information was
logged. This commit moves the command logging up to before we enter the
if block where the win_runas code would be executed, restoring the
prior logging behavior.
* Reword and clarify usage, clients & arg/kwarg, and content negotiation
* Replace all urlencoded examples with JSON examples
Using urlencoded format is a fast shorthand at the CLI with curl but it
should really be avoided for any real work. It requires having to know a
lot about the limitations and use of the format, and for complex tasks
it requires knowing a lot about how Salt's CLI `name=val` string parsing
works. It causes a lot of confusion and support issues and it should be
the exception, not the rule.
* Add one more mention of the full list of client interfaces
