This repository is home to the Operations Engineering's tools and utilities for managing, monitoring, and optimising software development processes at the Ministry of Justice. • This repository is defined and managed in Terraform
As a Operations Engineering Team
I want to know how to delete a Hostedzone now that we are managing DNS in code
so that what we manage in code is teh same as what is in AWS Route53
Value
OctoDNS doesn't currently support deletion of Hostedzone (you can only delete DNS records in the zone and not the zone itself). Therefore we must have a clear, documented and repeatable process to ensure that we can safely delete Hostedzones when required.
This is not likely to happen often, as in most cases we don't delete Hostedzones. They will normally either home a redirect if a service has been replaced or be converted to a defensive domain. We may delete a zone if ownership is transferred to another organisation i.e. another Government Department, or tidy up if we have been creating zones for testing purposes.
We are also creating automation that alerts when potential unused zones are identified. One outcome of that process would be deletion, upon which this process would be used.
Functional Requirements (What):
[ ] Runbook for how to delete a Hostedzone in the context of IAC
Non-Functional Requirements (How):
[ ] Agree process for deletion (currently remove DNS values from YAML file, then delete Directory, then manually delete in AWS - But is there a better way?).
[ ] Maybe see if there is a way we can automate this requirement.
User Need
As a Operations Engineering Team I want to know how to delete a Hostedzone now that we are managing DNS in code so that what we manage in code is teh same as what is in AWS Route53
Value
OctoDNS doesn't currently support deletion of Hostedzone (you can only delete DNS records in the zone and not the zone itself). Therefore we must have a clear, documented and repeatable process to ensure that we can safely delete Hostedzones when required.
This is not likely to happen often, as in most cases we don't delete Hostedzones. They will normally either home a redirect if a service has been replaced or be converted to a defensive domain. We may delete a zone if ownership is transferred to another organisation i.e. another Government Department, or tidy up if we have been creating zones for testing purposes.
We are also creating automation that alerts when potential unused zones are identified. One outcome of that process would be deletion, upon which this process would be used.
Functional Requirements (What):
Non-Functional Requirements (How):
Acceptance Criteria: