Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Should have option to gracefully handle existing A record for CNAME create #18
When doing a
Obviously we can't expect Chef to continue, as that might throw off expectations, but an extra option
Use case that runs into this:
our nodes can be created on both EC2 or other external hosts. If on EC2, we create a CNAME record for the by amazon provided DNS record (like
Switching between ec2 and non-ec2, you'd have to manually remove the records before continuing.
The CNAME validation was a recent addition. The only concern I have with the proposal is that it might not only be an A record in the way. For example, there could be MX, CNAME, NS or any other type of record for that matter. I wonder if the risks associated with forcefully removing those records is too high?
@aeden does it error on MX/NS as well? I thought (although I am highly uninformed on anything DNS non-trivial) you should be allowed to have a CNAME record on top of MX/NS, as they are for different purposes.
I agree that it might be a high risk. Maybe a different solution would fit. Maybe a better solution would be to bundle some library helpers that help you check for existing records? You can then do what ever you want with those checks, but I'd wrap them in a
Ideally, there'd be some kind of