v1 record description not accessible in v2 API

Bug #1466568 reported by Joe McBride
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Designate
Fix Released
High
Federico Ceratto

Bug Description

Expected Result
When creating a description for a record in the v1 API, a user probably expects the description should be accessible via the v2 API.

Actual Result
The description can not be accessed or modified.

Steps to reproduce
Create a record in v1.
Get the record via the recordset in v2.
The description field is only available as an attribute of the zone or recordset. When the v1 api is accessed, a recordset description can not be accessed.

Acceptable Fix:
Add a note to REST documentation for v1 and v2 APIs about this issue.

Kiall Mac Innes (kiall)
Changed in designate:
status: New → Triaged
importance: Undecided → High
milestone: none → liberty-1
Kiall Mac Innes (kiall)
tags: added: low-hanging-fruit
Thierry Carrez (ttx)
Changed in designate:
milestone: liberty-1 → liberty-2
Changed in designate:
assignee: nobody → pradeep kumar singh (pradeep-singh-u)
Changed in designate:
assignee: pradeep kumar singh (pradeep-singh-u) → Federico Ceratto (federico-ceratto)
Changed in designate:
status: Triaged → In Progress
Changed in designate:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in designate:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in designate:
milestone: liberty-2 → 1.0.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.