The directory tools is exculed for runing pep8 test now.
Enable pep8 to check files in toos/ since there will be more python files.
Change-Id: I49b8b90ab8db82033c5a45ee2bcbfbfb7fb77339
"# flake8: noqa" option disables all checks for the whole file.
To disable one line we should use "# noqa".
Remove unused "# flake8: noqa" and fix hidden hacking errors.
Change-Id: I8b26cb0e7e5ad4a838099c7aa3ced31b96f28ca2
Closes-Bug: #1540254
Also update hooks to use murano install_venv and update script to fix
all the typos
Co-Authored-By: Nikolay Starodubtsev <starodubcevna@gmail.com>
Co-Authored-By: Victor Ryzhenkin <vryzhenkin@mirantis.com>
Closes-Bug: #1536614
Change-Id: I17de28570d543d30e80d41113425e32b0f4c26b2
Currently file lacks executable bit in its permission, so running tox -e
cover raises a Permission Denied error.
This patch adds executable bit for every group
Change-Id: I99dab1b0e2df9a9346e1017cc11c8c11f29a5865
Closes-Bug: #1476035
This script will allow to run non voiting coverage job which will detect
any changes in the code coverage for each commit on review.
It will help to automatically control the unit tests coverage for each commit
and core team can ask to add unit tests to some commit which will require it.
Change-Id: I318a6b0133333ef16494ed2def512720b15ce956
Closes-Bug: #1473364
* support scripts were copied from other projects like cinder, ...
* some modification were made to support some code checks
* at first we focus on code issues classified as 'refactor'
* job compare sets of code issues of current and previous commit
* if new issue emerged in current commit then -1
* use tox to launch locally 'tox -e pylint'
* next step is to create non-voting gate job
* job can be tested locally, example:
* 1) create method with more then 5 arguments
* 2) commit the change
* 3) run 'tox -e pylint'
* job should fail on 'Too many arguments'
Change-Id: Iccfb842de92e2284bedcfc7d9b1df5f456ba9d14
If subunit installed from packages then subunit-trace goes to
/usr/bin/ dir with hasbang string #!/usr/bin/python
In this case even if called from venv it use system python
interpreter, and will not have access to modules from venv.
Change-Id: I9b152055c5ce958001e59908564a3549960a7df9
Similarly with the way it was done in the murano-agent, added
the ability to use the oslo-config-generator for creating a sample
configuration file murano.conf.sample.
Now to create the file, you must run:
tox -egenconfig
Change-Id: I8b06336d75eccfd598ce9033333884f75f393a09
Some parameters were ommitted in murano sample config file
This patch adds config params from openstack to config checker
Closes-Bug: #1356787
Change-Id: I8221bc3aa063ecb53e210adf7a2222c92da1c049
Adds ability for deploy-time auth checks to allow/disallow
functionality, in line with other openstack projects.
Includes update of code in openstack/common, which is why the
patchset is so large. oslo-incubator changeset is May 27th
caed79d8239679cb74476bb0d9e5011b4fcc39da.
Implements blueprint policy-checks-in-api
Change-Id: I67a431dcc74f0a77ed48b7a489136d5008773cea
The previous commit, 3362ee1337d47ab8930407c58311a811d471a7a4,
a sync with Openstack Common, removed all definitions of the
post_process() function from the Distro class and all of its
child classes in install_venv_common.py.
This fix simply removes the call to the function in
install_venv.py
The issue is similar to #1263940 in tempest:
https://bugs.launchpad.net/tempest/+bug/1263940
Change-Id: Iedd0c29789c4b2ab9be880f9bd320b39a9bdd277
Closes-Bug: #1307705
