)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":32962,"name":"Jakob Meng","email":"code@jakobmeng.de","username":"jakobmeng@web.de"},"change_message_id":"b9cbcec1b32df6c2081e8946ebb9a095a5dd9928","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"430d673c_05ea3f46","updated":"2022-07-27 11:34:50.000000000","message":"Ansible collection community.vmware implemented the same workaround:\n\nhttps://github.com/ansible-collections/community.vmware/commit/04bb7bf6f1693958957fef41452c25b203a40424","commit_id":"759360d582667f68af84cdde72ed796ba4923529"},{"author":{"_account_id":32962,"name":"Jakob Meng","email":"code@jakobmeng.de","username":"jakobmeng@web.de"},"change_message_id":"9383628fbd5777288edea4374530e293b7d41ee4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"59ed0cac_dbf13f0b","updated":"2022-07-27 11:20:53.000000000","message":"This is at least required until we drop compatibility with Ansible 2.9 in [1]. Once we drop compatibility with Ansible 2.9 we can replace the whole block and only keep:\n\n    from ansible.module_utils.compat.version import StrictVersion\n\n\n[1] https://review.opendev.org/c/openstack/ansible-collections-openstack/+/850463","commit_id":"759360d582667f68af84cdde72ed796ba4923529"}]}