Actions
Refactor #18398
openUse consistent naming of parameters in the DNS modules
Status:
Ready For Testing
Priority:
Normal
Assignee:
Category:
DNS
Target version:
-
Description
This comes from https://github.com/theforeman/smart-proxy/pull/490. Currently the API uses parameter names like fqdn which are ambiguous, in particular in the context of a CNAME where both the name and content are FQDNs.
To avoid confusion I'm proposing to use the following naming scheme:
- fqdn is what is defined in the API and should only be in dns_api.rb
- value is what is defined in the API and should only be in dns_api.rb
- name is the DNS name you query for
- content is the result your DNS server should return
Actions