
This change adds a basic bandit config for Swift. It can be invoked by running the tox environment for bandit; tox -e bandit This is an initial step for using bandit with Swift and it should be revisited to improve the testing as more is learned about the specific needs of the Swift code base.As per now some tests are excluded as they were used on purpose. https://wiki.openstack.org/wiki/Security/Projects/Bandit Implements: blueprint swift-bandit Change-Id: I621be9a68ae9311f3a6eadd1636b05e646260cf2
19 lines
447 B
Plaintext
19 lines
447 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
|
|
# Hacking already pins down pep8, pyflakes and flake8
|
|
hacking>=0.8.0,<0.9
|
|
coverage
|
|
nose
|
|
nosexcover
|
|
nosehtmloutput
|
|
oslosphinx
|
|
sphinx>=1.1.2,<1.2
|
|
mock>=1.0
|
|
python-swiftclient
|
|
python-keystoneclient>=1.3.0
|
|
|
|
# Security checks
|
|
bandit>=0.10.1
|