4250756a1f
Under monasca_common/policy an enforcement engine is added for using oslo.policy in the other monasca projects. There are same methods as in enforcement engings currently used in nova and keystone projects. Also added unit tests under tests/policy for testing implemented methods. Task: 6105 Story: 2001233 Change-Id: Ic5402ba0986416c9386c1dc3fc1559f148ea9625 Signed-off-by: Amir Mofakhar <amofakhar@op5.com>
20 lines
718 B
Plaintext
20 lines
718 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
|
|
bandit>=1.1.0 # Apache-2.0
|
|
hacking!=0.13.0,<0.14,>=0.12.0 # Apache-2.0
|
|
Babel!=2.4.0,>=2.3.4 # BSD
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
httplib2>=0.9.1 # MIT
|
|
mock>=2.0.0 # BSD
|
|
mox>=0.5.3 # Apache-2.0
|
|
oslo.context>=2.19.2 # Apache-2.0
|
|
oslotest>=1.10.0 # Apache-2.0
|
|
os-testr>=1.0.0 # Apache-2.0
|
|
requests-mock>=1.1.0 # Apache-2.0
|
|
testrepository>=0.0.18 # Apache-2.0/BSD
|
|
testscenarios>=0.4 # Apache-2.0/BSD
|
|
testtools>=2.2.0 # MIT
|