yahoo-eng-team team mailing list archive

[Erno Kuvaja <jokke@xxxxxx>]

I do not think we should artificially limit something that does work
just based on the fact that we do not explicitly state supporting it.
There is clear difference between the two statements "we do not support
this" and "we guarantee that this will not work".

I will close this for now. Please feel free to reopen if you have some
other concerns around this than "violates api".

** Changed in: glance
       Status: In Progress => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1400366

Title:
  Glance allows to sort images by private fields

Status in OpenStack Image Registry and Delivery Service (Glance):
  Opinion

Bug description:
  Glance api supports sorting only by 'name', 'status', 'container_format',  'disk_format', 'size', 'id', 'created_at', 'updated_at'
  But now it's possible to make sorting by private fields like checksum or min_ram (/images?sort_key=checksum), that violates api.

  It's possible because there is no key validation on the api layer in v2. 
  There is a check on the db in pagination, but it covers all the fields (not only api), which causes a problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1400366/+subscriptions