-
Notifications
You must be signed in to change notification settings - Fork 472
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DNS checks should have hostname as attribute, not key #518
Comments
The same issue affects HTTP tests, as well, since the URL is held in the key and this prevents you from running the same URL test against different backends or with different header sets. |
I'll try doing something on this over xmas, I'm stuck in the office on call while everything's quiet. |
Thinking this should be done for all resources at this point. Another usecases: #339 Maybe this ticket should be a generic one for all resources? |
Two years and I've still not been able to work on this. I blame covid for giving me more work, and lack of motivation... |
Describe the feature:
Currently, DNS checks specify the hostname to resolve as a key. The server name to use for resolving is an attribute. However, if you want to test the same item resolving on multiple DNS servers you cannot do it as the resolving hostname is a unique key in the heira.
Describe the solution you'd like
As previously done with the exec resource, I would like to add a new attribute 'resolve' which optionally holds the hostname to resolve, overriding the key. This will allow structures such as:
which will allow you to check correct name resolution from multiple DNS hosts, which is not currently possible.
I also believe that keeping the keys as symbolic only is a better way to work, with all the test definition held in the attributes, as this allows better control when merging.
Describe alternatives you've considered
It would be possible to use different resolution targets on different DNS servers, but this seems untidy, and may cause automation or scaling problems.
The text was updated successfully, but these errors were encountered: