Zone filtering by TTL, Description & Status
Bug #1466545 reported by
Joe McBride
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Fix Released
|
Low
|
Mimi Lee |
Bug Description
This may be more of a minor enhancement request:
*Expected Result:*
When a client filters by ttl or description, the resulting list of zones should match the filter criteria.
*Actual Result:*
All zones are returned, regardless of whether they match.
*Steps to Reproduce:*
GET /v2/zones?ttl=100
GET /v2/zones?
*Additional Notes*
- It appears that zone status filtering is supported but is not documented at: http://
GET /v2/zones?
- GET /v2/zones/
tags: | added: low-hanging-fruit |
Changed in designate: | |
status: | New → Triaged |
importance: | Undecided → Low |
milestone: | none → liberty-2 |
Changed in designate: | |
status: | Triaged → In Progress |
Changed in designate: | |
status: | In Progress → Fix Committed |
Changed in designate: | |
status: | Fix Committed → Fix Released |
Changed in designate: | |
milestone: | liberty-2 → 1.0.0 |
To post a comment you must log in.
Add note about also adding ability to filter on recordset description: GET /v2/zones/ <id>/recordsets ?description= foo*