Conversation
|
remember, any changes you make to the API, make sure they're documented |
|
did this die on the operating table? |
|
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. |
|
Is this a deployment priority? |
|
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. |
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.