Skip to content

Conversation

@zeeman
Copy link
Contributor

@zeeman zeeman commented Jul 1, 2014

This is supposed to resolve #676. Right now I'm pretty sure this has unintended behavior if you want to use multiple ctnr filtering in combination with other filters.

@akeym
Copy link
Member

akeym commented Jul 2, 2014

remember, any changes you make to the API, make sure they're documented

@drkitty drkitty changed the title Api multiple filter arguments API multiple filter arguments Jul 8, 2014
@akeym
Copy link
Member

akeym commented Jul 31, 2014

did this die on the operating table?

@zeeman
Copy link
Contributor Author

zeeman commented Aug 2, 2014

It's not dead, but it's quite a bit more complex than I'd originally thought. In particular, allowing users to select multiple ctnr's and still filter by other parameters is gross. It would be good if I knew exactly what use cases I have to support.

@drkitty
Copy link
Contributor

drkitty commented Jan 16, 2015

Is this a deployment priority?

@akeym
Copy link
Member

akeym commented Feb 27, 2015

I'd like to see this resurrected at some point after deployment. The basic use-case, is for querying for objects in a list of containers. Many larger IT groups on campus have many containers and for some cases, they really don't care what the container is - they just want a list of every interface they have, or every X with attribute Y regardless of which container of theirs its in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

API allow multiple values for a query parameter

3 participants