At the moment, the plan code may be insufficiently tested to allow us to have confidence when making changes to it. We need to confirm that this code is covered with sufficient tests so that we can make changes to it confidently, as it is a crucial part of the DNS Operator.
Refinement thoughts:
- Use a code coverage tool for a first impression of areas that are not well tested.
- Unit tests to cover a broad array of possible (albeit unlikely) scenarios.
- Are there are areas where the plan can be rewritten more opinionated for our specific use-cases.
- e.g. de-duplicate the providers
- remove unreachable code
- parts of external-dns that only exist for use-cases we don't have
At the moment, the plan code may be insufficiently tested to allow us to have confidence when making changes to it. We need to confirm that this code is covered with sufficient tests so that we can make changes to it confidently, as it is a crucial part of the DNS Operator.
Refinement thoughts: