Add request_ids attribute to resource objects

Bug #1549009 reported by OpenStack Infra
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-cinderclient
Invalid
Undecided
Unassigned

Bug Description

https://review.openstack.org/257199
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/python-cinderclient" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit ec65605eded61801b817cc1e556de0ae8cb74f7c
Author: Ankit Agrawal <email address hidden>
Date: Sun Dec 13 23:59:38 2015 -0800

    Add request_ids attribute to resource objects

    Added request_ids attribute to resource object for all the
    cgsnapshots, consistencygroups, qos_specs, quota_classes,
    quotas and services APIs by updating following APIs:

    cgsnapshots: delete, update
    consistencygroups: delete, update, create
    qos_specs: delete, associate, disassociate, disassociate_all
    quota_classes: update
    quotas: update
    services: enable, disable, disable_log_reason

    These changes are required to return 'request_id' from client to
    log request_id mappings of cross projects.

    For more details on how request_id will be returned to the caller,
    please refer to the approved blueprint [1] discussed with the
    cross-project team.
    [1] http://specs.openstack.org/openstack/openstack-specs/specs/return-request-id.html

    DocImpact
    'request-ids' will be returned as an attribute with response object.
    User can access it using 'res.request_ids' where 'res' is a
    response object.

    Change-Id: I7b399512fcec9ecd31938656deb60e325bb76ad4
    Partial-Implements: blueprint return-request-id-to-caller

Revision history for this message
Sean McGinnis (sean-mcginnis) wrote :

I don't see documentation that needs to be updated with this.

Changed in python-cinderclient:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.