v1 API always gives null for record descriptions, despite v2 recordset having a description?
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Invalid
|
Undecided
|
Unassigned |
Bug Description
For example:
krenair@silver:~$ curl -H "Content-Type: application/json" -H "x-auth-token: redacted" -H "x-auth-
{
"created_at": "2016-08-
"data": "instance-
"description": null,
"domain_id": "933a78c2-
"id": "28c927b6-
"name": "185.128-
"priority": null,
"ttl": null,
"type": "PTR",
"updated_at": "2016-08-
}
krenair@silver:~$ curl -H "Content-Type: application/json" -H "x-auth-token: redacted" -H "x-auth-
{"status": "ACTIVE", "description": "MANAGED BY dns-floating-
I noticed this issue because I tried to edit a record in Horizon (which uses the v1 API via python-
Interestingly the v2 API gives a null updated_at whereas the v1 one does not. Maybe this is because of recordsets vs. records? I did notice the IDs were different... I think I'd still expect every record be created with the description of the recordset. Hmm.
So, records and recordsets are 2 distinct resources.
When we changed to v2, records became a sub resource of recordsets, and we did some things in the v1 API to allow it to continue working.
However, the descriptions for recordsets cannot be shown on records, as they can have their own description, which is unfortunately hidden in the v2 API.