As described in the description we are not able to follow implementation decided in cross-project specs [1] in glance. To overcome this Stuart has suggested to use hooks in comment #5 for which we have added a patch [2].
As of now Brant has come-up with a solution where we can use object-proxy wrapper from wrapt module to return the request-id to the caller. This solution is kind of similar to what we have proposed in cross-project specs [1]. I have a POC [3] for this patch for which Erno has raised his concern for returning all request-ids in case of pagination. I am working to resolve his concern.
Hi All,
Summary for current status of this specs-lite:
As described in the description we are not able to follow implementation decided in cross-project specs [1] in glance. To overcome this Stuart has suggested to use hooks in comment #5 for which we have added a patch [2].
As of now Brant has come-up with a solution where we can use object-proxy wrapper from wrapt module to return the request-id to the caller. This solution is kind of similar to what we have proposed in cross-project specs [1]. I have a POC [3] for this patch for which Erno has raised his concern for returning all request-ids in case of pagination. I am working to resolve his concern.
[1] http:// specs.openstack .org/openstack/ openstack- specs/specs/ return- request- id.html /review. openstack. org/#/c/ 261288 /review. openstack. org/#/c/ 316052/ 2
[2] https:/
[3] https:/