2017-03-02 20:09:39 +01:00
|
|
|
# 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!=0.13.0,<0.14,>=0.12.0 # Apache-2.0
|
|
|
|
bashate>=0.2 # Apache-2.0
|
|
|
|
PyYAML>=3.10.0 # MIT
|
2019-06-06 15:25:15 +10:00
|
|
|
ansible-lint>=4.1.0
|
2018-06-15 13:58:57 +10:00
|
|
|
openstacksdk
|
2018-08-20 13:32:23 +10:00
|
|
|
zuul-sphinx>=0.2.3
|
2018-11-01 15:31:44 +11:00
|
|
|
testtools
|
|
|
|
mock
|
2018-10-19 14:00:07 -07:00
|
|
|
# testinfra 1.17.0 has a broken wheel that won't install under python3
|
2019-05-06 13:10:44 +10:00
|
|
|
# testinfra 3.0.0 switched the ansible backend, but broke ipv6 handling
|
|
|
|
testinfra!=1.17.0,!=3.0.0
|
2019-06-03 11:52:55 +10:00
|
|
|
# testinfra's ansible backend actually requires paramiko, but it's not
|
|
|
|
# specified. After
|
|
|
|
# https://github.com/philpep/testinfra/pull/454
|
|
|
|
# releases we can do testinfra[ansible] here instead
|
|
|
|
ansible>=2.8.0
|
|
|
|
paramiko
|
|
|
|
|