)]}'
{"neutron_lib/api/definitions/sfc_servicegraph.py":[{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"8355c923814e89a6507515496fb27f221c7e9116","unresolved":true,"context_lines":[{"line_number":27,"context_line":"IS_SHIM_EXTENSION \u003d False"},{"line_number":28,"context_line":"IS_STANDARD_ATTR_EXTENSION \u003d False"},{"line_number":29,"context_line":"NAME \u003d \"Service Graph extension.\""},{"line_number":30,"context_line":"DESCRIPTION \u003d \"Service Graph extension.\""},{"line_number":31,"context_line":"UPDATED_TIMESTAMP \u003d \"2017-09-20T00:00:00-00:00\""},{"line_number":32,"context_line":"API_PREFIX \u003d sfc.API_PREFIX"},{"line_number":33,"context_line":"SERVICE_GRAPH \u003d \u0027service_graph\u0027"}],"source_content_type":"text/x-python","patch_set":1,"id":"9dd65dd5_f714115e","line":30,"updated":"2026-05-07 14:26:10.000000000","message":"Should name and description reference SFC as the tap one does? Although this is just a migration.","commit_id":"63b0fc9ce53264c49a31fdf8c3595da5c637c015"}]}
