Support EC2 filters
We should support EC2 filters, if for no other reason than for API compatibility with EC2.
However, this actually goes much further. I'm referencing here my proposed merge:
https:/
The patch was architected with a separation of the AWS filterspec from an underlying predicate, so it could also support filters in the OpenStack API if we can agree an API format.
(If we are going to discuss adding filter support to the OpenStack API, then I think we'll need a full "Discussion" session)
Taken further, these filters could dramatically simplify and harmonize a lot of our code, by using functions that take predicates rather than a long list of similar functions varying only in their arguments. (fetch_
Blueprint information
- Status:
- Complete
- Approver:
- Vish Ishaya
- Priority:
- Undefined
- Drafter:
- justinsb
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Deferred
- Milestone target:
- None
- Started by
- Completed by
- Vish Ishaya