)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":25023,"name":"Jonathan Rosser","email":"jonathan.rosser@rd.bbc.co.uk","username":"jrosser"},"change_message_id":"4164ab4eb71aeb7a767802a711fd795a218ff54c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"30232092_9ee6f914","updated":"2022-01-04 14:04:39.000000000","message":"There are two mechanisms in play here, first using a local git repo or fork like you describe, but there is also the possibility to put a u-c file in /etc/openstack-deploy/.... as described in this releasenote https://review.opendev.org/c/openstack/openstack-ansible/+/774523/10/releasenotes/notes/repo-server-uc-cache-74de275bfd82c998.yaml#14\n\nThere are a couple of reasons for this, the example in the reno is running master branch magnum on a stable release installation, and another use case would be like ours where we want to take the wallaby u-c file and simply adjust one entry. Putting a copy of just the u-c file in /etc/openstack-deploy allows it to be kept in version control along with the rest of the deployment config, if desired.","commit_id":"a749517ffbb511fb51c76d46da39a64a72d78805"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"5f6f6b0138b5675960d71f76c246ff0b80e47a19","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"def813d3_3e5e01d0","in_reply_to":"30232092_9ee6f914","updated":"2022-01-13 12:20:58.000000000","message":"Tbh I\u0027d say that we need to restore functionality of global-requirement-pins.txt 😞\n\nFeels that for this purpose we\u0027d need to move filtering from independent roles to python_venv_build and drop from u-c anything that is contained in venv_build_global_constraints","commit_id":"a749517ffbb511fb51c76d46da39a64a72d78805"},{"author":{"_account_id":31542,"name":"Andrew Bonney","email":"andrew.bonney@bbc.co.uk","username":"andrewbonney"},"change_message_id":"9d392adc3c1517d3a6c19f307e790ec68f4c3a12","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"ce5f24fc_c897fb6b","in_reply_to":"def813d3_3e5e01d0","updated":"2022-01-13 12:58:11.000000000","message":"I had chosen not to document the option to drop a file in /etc/openstack_deploy as it still requires you to locate (and keep up to date) the upper constraints file from the git repo, so it seemed slightly less prone to error to perform a clone or maintain a fork rather than drop in a static file that might be forgotten about.","commit_id":"a749517ffbb511fb51c76d46da39a64a72d78805"}]}