summaryrefslogtreecommitdiff
path: root/tox.ini
diff options
context:
space:
mode:
authorEric Brown <browne@vmware.com>2016-03-08 16:27:05 -0800
committerEric Brown <browne@vmware.com>2016-03-08 16:27:05 -0800
commite28fb14a7c20713278a54064f3b8d7de24b90574 (patch)
treec7dda45c3c395c2e74702f6982f08af861ea7f24 /tox.ini
parent45ffe4ee20849e546710d188d403545deebe37f0 (diff)
downloadkeystone-e28fb14a7c20713278a54064f3b8d7de24b90574.tar.gz
Explicitly exclude tests from bandit scan
Now that the bandit linter runs without a bandit.yaml specified, it should exclude the tests directory similar to how it did before in the bandit.yaml. The reason this has not caused a problem yet is because bandit is still finding a config bandit.yaml in .tox/pep8/etc/bandit/bandit.yaml. But in a newer version of bandit this will not be the case. Change-Id: Ie81d052cd57318a987f0ebfe718e1c01bdbffcd3
Diffstat (limited to 'tox.ini')
-rw-r--r--tox.ini4
1 files changed, 2 insertions, 2 deletions
diff --git a/tox.ini b/tox.ini
index 760029767..e5d2b13ec 100644
--- a/tox.ini
+++ b/tox.ini
@@ -51,13 +51,13 @@ commands =
bash -c "find keystone -type f -regex '.*\.pot?' -print0| \
xargs -0 -n 1 msgfmt --check-format -o /dev/null"
# Run security linter
- bandit -r keystone
+ bandit -r keystone -x tests
[testenv:bandit]
# NOTE(browne): This is required for the integration test job of the bandit
# project. Please do not remove.
deps = .[bandit]
-commands = bandit -r keystone
+commands = bandit -r keystone -x tests
[testenv:cover]
commands =