
A lot of openstack components like: - solum - tosca-parser - heat - murano - etc... reimplement theirs own yaml parser for loading and dumping. These implementations sometimes forgot to use a safe loader or safe dumper, our implementation use safe by default. You can deactive safe by passing the argument is_safe to false when you call oslo_serialization.yamlutils.load or oslo_serialization.yamlutils.dump. Change-Id: I63e85a2b4fc999e6acac12ae51c2ab8c64bddbc6 Co-Authored-By: Natal Ngétal <hobbestigrou@erakis.eu>
16 lines
654 B
Plaintext
16 lines
654 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.
|
|
|
|
# NOTE(harlowja): Because oslo.serialization is used by the client libraries,
|
|
# we do not want to add a lot of dependencies to it. If you find that
|
|
# adding a new feature to oslo.serialization means adding a new dependency,
|
|
# that is a likely indicator that the feature belongs somewhere else.
|
|
|
|
pbr!=2.1.0,>=2.0.0 # Apache-2.0
|
|
six>=1.10.0 # MIT
|
|
msgpack>=0.5.2 # Apache-2.0
|
|
oslo.utils>=3.33.0 # Apache-2.0
|
|
pytz>=2013.6 # MIT
|
|
PyYAML>=3.12 # MIT
|