python-keystoneclient

we should allow updating object attributes to None

Bug #1410024 reported by wanghong
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-keystoneclient
Won't Fix
Wishlist
Unassigned

Bug Description

Currently, all the v3 object managers are inherited from CrudManager. But CrudManager will clean up the None value parameters before sending request to keystone, refer to:
https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/base.py#L56

That is to say, we can't update object attributes to None. But, some times we really need to update them to None, such as parent_region_id of Region object, parent_id of Project object etc...

wanghong (w-wanghong)
summary: - we can't update object attributes to None
+ we should allow updating object attributes to None
Changed in python-keystoneclient:
assignee: nobody → wanghong (w-wanghong)
Morgan Fainberg (mdrnstm)
Changed in python-keystoneclient:
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Steve Martinelli (stevemar) wrote :

Automatically unassigning due to inactivity.

Changed in python-keystoneclient:
assignee: wanghong (w-wanghong) → nobody
Revision history for this message
Morgan Fainberg (mdrnstm) wrote :

This is stuff that should be focused on in SDK. KEystoneclient enhancements on this front will be minimally beneficial when we move everyone to SDK. Marking as wont fix.

Changed in python-keystoneclient:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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