auth: note that PRUNE/EXTEND are new in 4.9.12/5.0.2

Signed-off-by: Peter van Dijk <peter.van.dijk@powerdns.com>

diff --git a/docs/http-api/swagger/authoritative-api-swagger.yaml b/docs/http-api/swagger/authoritative-api-swagger.yaml
index 00ff9d1a36bb9cf4ed9b8fb125f2267ead0c6ee6..6714c81a711c618fd3b96bb3a74c106bad86fec4 100644 (file)
--- a/docs/http-api/swagger/authoritative-api-swagger.yaml
+++ b/docs/http-api/swagger/authoritative-api-swagger.yaml
@@ -1265,7 +1265,7 @@ definitions:
         description: 'DNS TTL of the records, in seconds. MUST NOT be included when changetype is set to “DELETE”.'
       changetype:
         type: string
-        description: 'MUST be added when updating the RRSet. Must be one of DELETE, EXTEND, PRUNE or REPLACE. With DELETE, all existing RRs matching name and type will be deleted, including all comments. With EXTEND, only a single record shall be present, and it will be added to the RRSet if not already present. With PRUNE, only a single record shall be present, and it will be deleted from the RRSet if present. With REPLACE, when records is present, all existing RRs matching name and type will be deleted, and then new records given in records will be created. If no records are left, any existing comments will be deleted as well. When comments is present, all existing comments for the RRs matching name and type will be deleted, and then new comments given in comments will be created.'
+        description: 'MUST be added when updating the RRSet. Must be one of DELETE, EXTEND, PRUNE or REPLACE. PRUNE and REPLACE are available since versions 4.9.12 and 5.0.2. With DELETE, all existing RRs matching name and type will be deleted, including all comments. With EXTEND, only a single record shall be present, and it will be added to the RRSet if not already present. With PRUNE, only a single record shall be present, and it will be deleted from the RRSet if present. With REPLACE, when records is present, all existing RRs matching name and type will be deleted, and then new records given in records will be created. If no records are left, any existing comments will be deleted as well. When comments is present, all existing comments for the RRs matching name and type will be deleted, and then new comments given in comments will be created.'
       records:
         type: array
         description: 'All records in this RRSet. When updating Records, this is the list of new records (replacing the old ones). Must be empty when changetype is set to DELETE, and must contain only one element when changetype is set to EXTEND or PRUNE. An empty list results in deletion of all records (and comments).'

diff --git a/docs/http-api/zone.rst b/docs/http-api/zone.rst
index 9711c2523ec6513fbde39899aaf6990baa0b7138..e3f4d30cf26ab2fcc8214e1d151b442936297425 100644 (file)
--- a/docs/http-api/zone.rst
+++ b/docs/http-api/zone.rst
@@ -137,6 +137,8 @@ Will yield a response similar to this (several headers omitted):
 Adding a single record to a RRset
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
+.. note:: added in versions 4.9.12 and 5.0.2
+
 .. code-block:: http
 
   PATCH /api/v1/servers/localhost/zones/example.org. HTTP/1.1
@@ -175,6 +177,8 @@ If no record with the same exact content exists in the RRSet, no action is perfo
 Deleting a single record from a RRset
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
+.. note:: added in versions 4.9.12 and 5.0.2
+
 .. code-block:: http
 
   PATCH /api/v1/servers/localhost/zones/example.org. HTTP/1.1