Designate/Blueprints/Recordset Record API Redesign

Overview
This blueprint proposes to eliminate the Records resource and only keep the RecordSets resource.

The API for recordsets and records is too complicated. Currently, a user is forced to create a recordset before creating a record. This leads to a confusing user experience. Users will create, get, update and delete recordsets. When the user creates a recordset the code will determine if it should be a new recordset. If all data is the same except for the record, a Duplicate error will be returned and the user will then add the Record by modifying the Recordset. The record will no longer be accessible as a separate resource; only as part of the recordset.

Currently, CNAME and DNAME record types cannot technically be a Recordset, because they cannot contain more than one record; however, in order to maintain consistency, we will be treating them as a Recordset.

Initially, there will only be a PUT and not a PATCH call available. The PUT will replace all the data in the Recordset, so if the user wants to add a record to a Recordset, the entire list of records will need to be submitted in the PUT request. There are plans to add json patch RFC6902 through a different blueprint. This will make it easier to add, delete and modify records within a Recordset.

The concept of a Resource Record Set is defined in RFC 2181, Section 5. To summarize, it says, each DNS Resource Record (RR) has four parts: label, class, type and data. Any records that have all four equal, should be rejected as duplicates. However, it is possible for most record types to exist with the same label, class and type, but with different data. Such a group of records is defined to be a Resource Record Set (RRSet). A query for a specific label, class and type, should always return all records in the associated RRSet. It further states that all RRs in a RRSet should have the same ttl.

Current API
/zones/{zone id}/recordsets/{recordset id}/records/{record id}

New API
/zones/{zone id}/recordsets/{recordset id}

List Recordset(s) (GET)
When no id is specified all recordsets for the specified zone are returned. No body is provided in the request. When a recordset id is provided, only that recordset is returned. No body is provided in the request

Response {   "recordset" : [ {       "created_at" : "2014-04-29T19:34:21.819615", "version" : 1, "zone_id" : "766d7605-4c48-41fa-a9de-76692ed8051c", "links" : { "self" : "http://192.168.33.8:9001/v2/zones/766d7605-4c48-41fa-a9de-76692ed8051c/recordsets/06c3a2de-4e23-4143-98ab-6bf6d41ded26" },       "ttl" : 3600, "updated_at" : null, "description" : null, "type" : "A", "id" : "06c3a2de-4e23-4143-98ab-6bf6d41ded26", "name" : "example.com.", "records" : [ "192.0.1.2",           "192.0.1.3"          ],        {          "created_at" : "2014-04-29T22:04:41.000000", "version" : 1, "zone_id":"766d7605-4c48-41fa-a9de-76692ed8051c", "links":{ "self":"http://192.168.33.8:9001/v2/zones/766d7605-4c48-41fa-a9de-76692ed8051c/recordsets/e862ddb2-58ee-431a-a3b5-6881a5e26465" },           "ttl":null, "updated_at":null, "description":null, "type":"CNAME", "id":"e862ddb2-58ee-431a-a3b5-6881a5e26465", "name":"www.example.com.", "records": [ "example.com." ]           }        ],        "links" : { "self" : "http://192.168.33.8:9001/v2/zones/766d7605-4c48-41fa-a9de-76692ed8051c/recordsets/" } }

Create a Recordset (POST)
When a new Recordset is created, the caller must supply the name, type and data, which varies depending on the type. If the name and type are the same as an existing RecordSet, the return code will be 204 Duplicate, even if the data (record) being sent is different. The user must use PUT to change the record information. It cannot be changed implicitly through a CREATE.

Request {   "recordset" : { "name" : "foo.example.com.", "type" : "A", "ttl" : 3600, "records" : [ "10.1.0.1"      ]    }  } Response {  "recordset" : [ {      "created_at" : "2014-05-01T19:34:21.819615", "version" : 1, "zone_id" : "766d7605-4c48-41fa-a9de-76692ed8051c", "links" : { "self" : "http://192.168.33.8:9001/v2/zones/766d7605-4c48-41fa-a9de-76692ed8051c/recordsets/06c3a2de-4e23-4143-98ab-6bf6d41ded12" },      "ttl" : 3600, "updated_at" : null, "description" : null, "type" : "A", "id" : "06c3a2de-4e23-4143-98ab-6bf6d41ded12", "name" : "foo.example.com.", "records" : [ "10.1.0.1"       ]   }

Modify a RecordSet / Modify Records(PUT)
The PUT request will replace all the records in the Recordset.

Request

{  "recordset" : { "ttl" : 3000 "records" : [ "10.1.0.5"      ]     }   }

Response

{ "recordset" : [ {     "created_at" : "2014-05-01T19:34:21.819615", "version" : 1, "zone_id" : "766d7605-4c48-41fa-a9de-76692ed8051c", "links" : { "self" : "http://192.168.33.8:9001/v2/zones/766d7605-4c48-41fa-a9de-76692ed8051c/recordsets/06c3a2de-4e23-4143-98ab-6bf6d41ded12" },     "ttl" : 3000, "updated_at" : 2014-05-04T19:34:21.819615, "description" : null, "type" : "A", "id" : "06c3a2de-4e23-4143-98ab-6bf6d41ded12", "name" : "foo.example.com.", "records" : [ "10.1.0.5"      ]  }

Delete a RecordSet (DELETE)
When deleting a RecordSet, the user must supply the id in the url. All records associated with a RecordSet are, also, deleted. The request body and return body are empty. A 204 is returned.