discrepancy in response of "check_*" methods

Bug #1808305 reported by Neha Alhat
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-keystoneclient
Won't Fix
Undecided
Unassigned

Bug Description

Description:
============

The 'check_tag' api from keystoneclient.v3.projects.py module returns True/False[1] but there are other places like[2][3] where similar "check_*" methods returns NotFound exception if the record doesn't exist. In case of "check_tag" method, even if the record doesn't exists, it returns "False".

To have consistency in response along all apis, need to add a deprecation warning first, and then change the response in next release such as add a @removals.remove and create a new function for the correct response.

[1]: https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/v3/projects.py#L334-L340
[2]: https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/v3/roles.py#L288
[3]: https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/v3/users.py#L247

Revision history for this message
Colleen Murphy (krinkle) wrote :

Thanks for reporting this. It's unfortunate that it's a bit inconsistent, but it is at least documented, and IMO not a tremendous burden. In general we're trying to move toward doing all new work in openstacksdk and not python-keystoneclient, and I think the hassle of going through the deprecation process for these modules outweighs the benefits of changing the interfaces. Therefore I'm closing this as "Won't Fix".

Changed in python-keystoneclient:
status: New → Won't Fix
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.