From 7e45bcc47d68cac19fdc68f7d604cffbca6a6054 Mon Sep 17 00:00:00 2001
From: Eric Brown <browne@vmware.com>
Date: Sat, 12 Mar 2016 20:01:36 -0800
Subject: [PATCH] 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: Ic2d6d5da7083936eb364f56fb23e09b5dbccebae
---
 tox.ini | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tox.ini b/tox.ini
index 7c1b1f54..c53ec267 100644
--- a/tox.ini
+++ b/tox.ini
@@ -11,7 +11,7 @@ deps=-r{toxinidir}/test-requirements.txt
 commands =
   flake8
   # Run security linter
-  bandit -r oslo_utils -n5
+  bandit -r oslo_utils -x tests -n5
 
 [testenv:venv]
 commands = {posargs}
@@ -24,7 +24,7 @@ commands = python setup.py test --coverage --coverage-package-name=oslo_utils --
 
 [testenv:bandit]
 deps=-r{toxinidir}/test-requirements.txt
-commands = bandit -r oslo_utils -n5
+commands = bandit -r oslo_utils -x tests -n5
 
 [flake8]
 ignore = E123,H405