Hello,
I'm trying to design the Google Cloud DNS provider for Fog, and the first
question I face is which collections to expose?
It seems that most DNS providers expose "records" and "zones", but at least
one has some extras. For example stormondemand also has "domains" and
"reverses".
Given that, I'm wondering how hard should I try to squeeze into that model
the concepts used by Google Cloud DNS (i.e. its "RR sets" and "changes"
resources)?
DNS.providers.each do |p|
begin
p p.to_s + " " + DNS[p].collections.to_s
rescue Exception => e
p p.to_s + " " + e.to_s
end
end
"aws [:records, :zones]"
"bluebox [:records, :zones]"
"dnsimple [:records, :zones]"
"dnsmadeeasy [:records, :zones]"
"dreamhost [:records, :zones]"
"dynect [:records, :zones]"
"hp wrong number of arguments(1 for 0)"
"linode [:records, :zones]"
"rackspace [:records, :zones]"
"rage4 wrong number of arguments(1 for 0)"
"stormondemand [:domains, :records, :reverses, :zones]"
"zerigo [:records, :zones]"
BTW, what's wrong with hp and rage4?
--
Marcin Owsiany -- Software Engineer
Google Poland z.o.o., ul. Emilii Plater no. 53, 00-113, Warsaw
Sąd Rejonowy dla m. st. Warszawy w Warszawie,
XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 0000240611.
NIP: 525-23-44-078, Kapitał zakładowy Spółki 400 000, 00 zł.
--
You received this message because you are subscribed to the Google Groups
"ruby-fog" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
