)]}'
{"openstack/placement/v1/resource_provider.py":[{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"66018b150c97540c9302b36a3a367719f4b5e6e8","unresolved":true,"context_lines":[{"line_number":89,"context_line":""},{"line_number":90,"context_line":"        return self"},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"    def fetch_allocations(self, session: adapter.Adapter) -\u003e Self:"},{"line_number":93,"context_line":"        \"\"\"Fetch all allocations made against this resource provider."},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"        :param session: The session to use for making this request"}],"source_content_type":"text/x-python","patch_set":2,"id":"746e2a0f_d4830ebf","line":92,"updated":"2026-09-14 21:46:28.000000000","message":"I\u0027m not sure this is the way to do this. Allocations are their own resource, and the only difference between this API and the `/allocations` is that this one hangs under a parent resource. By doing things this way, we get a dumb dict rather than a proper resource. It works, but I think we can do better.\n\nRather than doing this, how about we add an Allocation class? The api-ref for this is at https://docs.openstack.org/api-ref/placement/#allocations. If we do this, we can have either a `classmethod` to do the fetch for a resource provider\u0027s allocations or a subclass a lá `EndpointGroupEndpoint` from `openstack.identity.v3.endpoint`.","commit_id":"8a415e92937785f87cd6d58ece5fc038cd08d04f"}]}