From 6e8057a65b7e4f585c3e6adbdf6d8bce1dbde62c Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 14 May 2015 12:30:53 -0400 Subject: reponses --- ...ment_1_dfa93678644b72781afda4fdc9d0da31._comment | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 doc/todo/Manage_DNS_with_Route53/comment_1_dfa93678644b72781afda4fdc9d0da31._comment (limited to 'doc/todo/Manage_DNS_with_Route53') diff --git a/doc/todo/Manage_DNS_with_Route53/comment_1_dfa93678644b72781afda4fdc9d0da31._comment b/doc/todo/Manage_DNS_with_Route53/comment_1_dfa93678644b72781afda4fdc9d0da31._comment new file mode 100644 index 00000000..8836beaa --- /dev/null +++ b/doc/todo/Manage_DNS_with_Route53/comment_1_dfa93678644b72781afda4fdc9d0da31._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-05-14T16:18:37Z" + content=""" +I think this would be great. Patches accepted. + +If I were going to implement this, I'd use + +to write the propellor Property. + +A question is, what host would the Property be attached to? +One way to do it would be to make the property be called something like +`route53Controller`. So then you pick a host, or hosts, and give them this +property for a domain, and those hosts then take care of making the +necessary API calls to route53. Presumably some API keys will be needed +on those hosts, which can be provided via the privdata. + +I'm happy to offer advice on implementation, but don't plan to code this up +myself, as I'm happily self-hosting my DNS servers. +"""]] -- cgit v1.2.3