summaryrefslogtreecommitdiff
path: root/releasenotes/notes/Fix-Delete-back-end-zone-resources-upon-zone-deletion-da0051432c95c8e2.yaml
diff options
context:
space:
mode:
Diffstat (limited to 'releasenotes/notes/Fix-Delete-back-end-zone-resources-upon-zone-deletion-da0051432c95c8e2.yaml')
-rw-r--r--releasenotes/notes/Fix-Delete-back-end-zone-resources-upon-zone-deletion-da0051432c95c8e2.yaml9
1 files changed, 9 insertions, 0 deletions
diff --git a/releasenotes/notes/Fix-Delete-back-end-zone-resources-upon-zone-deletion-da0051432c95c8e2.yaml b/releasenotes/notes/Fix-Delete-back-end-zone-resources-upon-zone-deletion-da0051432c95c8e2.yaml
new file mode 100644
index 00000000..6ae1f966
--- /dev/null
+++ b/releasenotes/notes/Fix-Delete-back-end-zone-resources-upon-zone-deletion-da0051432c95c8e2.yaml
@@ -0,0 +1,9 @@
+---
+fixes:
+ - |
+ Currently designate does not provide zone specific option to delete the
+ zone resources (such as files) on the back-end (e.g. bind9) when the zone
+ is deleted. To fix this add a header ``x-designate-hard-delete`` which will
+ be used in the zone delete API to delete zone files on the back-end. This
+ is in addition to the existing per-pool configration option that will
+ override this new header option. This option is restricted for admin.