From c0a1b7c8929a3bf5ba722840fa81761f3b07a59f Mon Sep 17 00:00:00 2001
From: Eric Brown <browne@vmware.com>
Date: Sat, 12 Mar 2016 20:06:40 -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: I4fd5b0cc60309dfc207cdf2025caae37836391da
---
 tox.ini | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tox.ini b/tox.ini
index 8ed4656..a3dbda8 100644
--- a/tox.ini
+++ b/tox.ini
@@ -13,7 +13,7 @@ commands =
 commands =
   flake8
   # Run security linter
-  bandit -r oslo_log -n5
+  bandit -r oslo_log -x tests -n5
 
 [testenv:venv]
 commands = {posargs}
@@ -27,7 +27,7 @@ commands =
   coverage report --show-missing
 
 [testenv:bandit]
-commands = bandit -r oslo_log -n5
+commands = bandit -r oslo_log -x tests -n5
 
 [flake8]
 # E123, E125 skipped as they are invalid PEP-8.