Libcloud responder doesn't handle providers that include a trailing `.` in zone names.
tomprince opened this issue · 1 comments
tomprince commented
In particular, route53 suffers from this.
mithrandi commented
I haven't done any integration testing for Route 53 yet, because of https://issues.apache.org/jira/browse/LIBCLOUD-875, but hopefully this gets us one step closer to being able to do that.