With a job aliases.json file that looks pseudo-ish like this:
a: 123.group.vm (pretend this is the FQDNs)
b: q-s0.group.vm (returns all vms in an instance group that are healty)
c: *.group.vm (wildcard on instance group)
d: .group.vm (vm1d would match vm1.group.vm)
e: 123.group.vm, 234.group.vm (two FQDNs)
f: 1.1.1.1
All of these aliases potentially could resolve to 1.1.1.1. This PR will change a reverse ip lookup on 1.1.1.1 from only returning the FQDNS to returning a, e and f as well. It will match on exact FQDNs's or ips in the alias values and ignore the others.
:x:The commit (8596d82d16ac611f756ff317a85ac24daecf67e1 ,c891f86418b4310b9c5517b2cef6cdfceecb138d) is missing the User's ID, preventing the EasyCLA check. Consult GitHub Help to resolve. For further assistance with EasyCLA, please submit a support request ticket.
This PR addresses https://github.com/cloudfoundry/bosh-dns-release/issues/72
With a job aliases.json file that looks pseudo-ish like this: a: 123.group.vm (pretend this is the FQDNs) b: q-s0.group.vm (returns all vms in an instance group that are healty) c: *.group.vm (wildcard on instance group) d: .group.vm (vm1d would match vm1.group.vm) e: 123.group.vm, 234.group.vm (two FQDNs) f: 1.1.1.1
All of these aliases potentially could resolve to 1.1.1.1. This PR will change a reverse ip lookup on 1.1.1.1 from only returning the FQDNS to returning a, e and f as well. It will match on exact FQDNs's or ips in the alias values and ignore the others.