db648ad781
Following OpenStack Style Guidelines[1]: [H203] Unit test assertions tend to give better messages for more specific assertions. As a result, assertIsNone(...) is preferred over assertEqual(None, ...) and assertIs(None, ...) [1] http://docs.openstack.org/developer/hacking/#unit-tests-and-assertraises Change-Id: Ie8136f1be4a57272e64b0b360ee608aa270901f7 |
||
---|---|---|
doc/source | ||
muranopkgcheck | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
babel.cfg | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
murano-pkg-check
Murano package validator tool
After checking out tool from repository easiest method to run tool is to run
This command will display help for murano-pkg-validator
If you installed it from PYPI you can use: .. code-block:: shell murano-pkg-check -h
To run validator in directory apache-app just run: .. code-block:: shell murano-pkg-check apache-app
It will print all errors there are on package.
Will search for all packages under directory murano-apps. It will print all errors and warnings for all packages found.
- Free software: Apache license
- Documentation: http://docs.openstack.org/developer/murano-pkg-check
- Source: http://git.openstack.org/cgit/openstack/murano-pkg-check
- Bugs: http://bugs.launchpad.net/murano-pkg-check