* create a yamllint utils module. as well as a yaml module that will
eventually be yaml tools to help in troubleshooting yaml
functionality.
* included unit tests for the yaml module. also not happy about moving
from __salt__.module.function to __salt__["module.function"] for the
test to work
* added pre_render test and minor correct to heredoc in yamllint
* changelog
* fix tests running in py3.5, also try and fix pre-commit.
* attempt to fix pre-commit
* still trying to fix pre-commit.
* forgot freebsd, added yamllint to freebsd
* update adding versionadded and depends
* fix pre-commit?
* fix pre-commit
* attempt to fix pre-commit again
Co-authored-by: Megan Wilhite <mwilhite@vmware.com>
Use use the packaging requirements as version constraints to all other
requirements files which should include Salt's base requirements.
The nox sessions now don't install the base requirements since the "top"
requirements file includes the base requirements.
All of this, ensuring that the same versions are used on all of them.
* Pin to ``pip>=20.2.4,<21.2`` on the created virtualenvs
* Use the static requirements when installing salt into the virtualenv
This should fix the freebsd failures
* ``SaltVirtualEnv`` will always use ``USE_STATIC_REQUIREMENTS=1``
* Update to ``pytest-salt-factories==0.907.x``
* Remove the temporary ``StateReturnAsserts`` class.
In the process, a few functions from the ``state`` module are now
wrapped to allow a more pythonic assertion against it's returns through
``StateReturn``.
We also introduce ``MultiStateReturn`` for full state runs.
* Update tests that relied on ``StateReturnAsserts`` or it's pytest helper function
