Bump version to 1.5.2 (#2969)

Run through the motions; create manual pages. Run go generate for good
measure. Fix typo in Makefile.release while at it.

Signed-off-by: Miek Gieben <miek@miek.nl>
This commit is contained in:
Miek Gieben
2019-07-03 19:47:38 +01:00
committed by GitHub
parent bb9df3122d
commit d933f635af
12 changed files with 39 additions and 60 deletions

View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.nl
.TH "COREDNS-ROUTE53" 7 "April 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-ROUTE53" 7 "July 2019" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP
@@ -20,7 +20,6 @@ The route53 plugin can be used when coredns is deployed on AWS or elsewhere.
.nf
route53 [ZONE:HOSTED\_ZONE\_ID...] {
[aws\_access\_key AWS\_ACCESS\_KEY\_ID AWS\_SECRET\_ACCESS\_KEY]
upstream
credentials PROFILE [FILENAME]
fallthrough [ZONES...]
}
@@ -41,9 +40,6 @@ to be used when query AWS (optional). If they are not provided, then coredns tri
AWS credentials the same way as AWS CLI, e.g., environmental variables, AWS credentials file,
instance profile credentials, etc.
.IP \(bu 4
\fB\fCupstream\fRis used for resolving services that point to external hosts (eg. used to resolve
CNAMEs). CoreDNS will resolve against itself.
.IP \(bu 4
\fB\fCcredentials\fR is used for reading the credential file and setting the profile name for a given
zone.
.IP \(bu 4
@@ -61,16 +57,14 @@ only queries for those zones will be subject to fallthrough.
.SH "EXAMPLES"
.PP
Enable route53 with implicit AWS credentials and an upstream:
Enable route53 with implicit AWS credentials and and resolve CNAMEs via 10.0.0.1:
.PP
.RS
.nf
\&. {
route53 example.org.:Z1Z2Z3Z4DZ5Z6Z7 {
upstream
}
route53 example.org.:Z1Z2Z3Z4DZ5Z6Z7
forward . 10.0.0.1
}