)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"94593baf75889cc7bed369b69c3f091f67df88de","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"d89ba216_73f1bbb6","updated":"2024-07-31 23:49:42.000000000","message":"I don\u0027t think we should implement this in this way.\nThis code reaches into the Octavia internal database and driver classes.\n\nI think it would be best to move this to the OVN provider repo and instead of using Octavia internals, use the Octavia API to get the appropriate list of load balancers[1] and use octavia_lib to get any required driver data structures (if the API does not provide what you need).\n\nThis does a few things:\n1. It keeps a stable API between the tool and Octavia.\n2. It means we don\u0027t have to expand the provider driver interface for \"sync\".\n2. It ensures the users of the tool has a valid Keystone token with the proper access level.\n3. It makes the tool available for stable branches.\n\nI don\u0027t think we should be putting tools into the main Octavia repository that are specific to a third party driver.\n\n[1] https://docs.openstack.org/octavia/latest/contributor/guides/providers.html#get-resource-support","commit_id":"ff79e16a56c82007e0f33c1597c7ba565a9ece5c"}]}