This fix updates:
- github.com/miekg/dns from 1.1.12 to 1.1.14
- google.golang.org/grpc from 1.21.0 to 1.21.1
- github.com/aws/aws-sdk-go from 1.19.41 to 1.20.3
- github.com/prometheus/common from 0.4.1 to 0.6.0
- gopkg.in/DataDog/dd-trace-go.v1 from 1.14.0 to 1.15.0

This fix fixes #2899
This fix fixes #2900
This fix fixes #2901
This fix fixes #2902
This fix fixes #2903
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>

* plugin/file: document using an explicit origin

See #2880
Signed-off-by: Miek Gieben <miek@miek.nl>

* Code review comments
Signed-off-by: Miek Gieben <miek@miek.nl>

* add circleci

* make ci work

* use existing script for setup

* add sep step for getting CI repo

Signed-off-by: Xiao An <hac@zju.edu.cn>

Signed-off-by: Xiao An <hac@zju.edu.cn>

* plugin/cache: remove item.Autoritative

Confuses clients if not set; remove it.
Signed-off-by: Miek Gieben <miek@miek.nl>

* Add extra comments on why we do this
Signed-off-by: Miek Gieben <miek@miek.nl>

This fix is a follow up on comment https://github.com/coredns/coredns/pull/2868#discussion_r291609761Signed-off-by: Yong Tang <yong.tang.github@outlook.com>

While running make encountered the following error:
```
$ docker run -i -t --rm -v $PWD:/v --net=host -w /v golang:1.12 make
...
...
** presubmit/test-lowercase
plugin/kubernetes/metadata_test.go:			t.Errorf("case %d expected metadata %v and got %v", i, tc.Md, md)
** presubmit/test-lowercase: please start with an upper case letter when using t.Error*()
Makefile:62: recipe for target 'presubmit' failed
make: *** [presubmit] Error 1
```
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>

- Fixes #2862

* Publish metadata from kubernetes plugin

* stickler fix

* Add a couple tests

* Add metadata section to README

* Update plugin/kubernetes/README.md
Co-Authored-By: Chris O'Haver <cohaver@infoblox.com>

* Address nit

Add OnRestartFailed to the ready plugin and some various cleanups.

Document slightly better how things are supposed to work with multiple
`ready`'s in the multiple Server Blocks.

All manually tested with this Corefile:
~~~
. {
    log
    ready
}

example.org {
    log
    chaos
    ready
}
~~~
And then `kill -SIGUSR1` and curling the ready endpoint. This works
well, the FailedReload is triggered by adding a syntax error in the
Corefile.

See #2659
Signed-off-by: Miek Gieben <miek@miek.nl>

This reverts commit a657e1f6.

otherwise the connection and associated socket stay in the CLOSE_WAIT
state unless/until golang runtime performs GC.

This fix updates several direct dependencies (grpc, aws, protobuf) in go mod,
and removed duplicates with `go mod tidy`

Note: tracing related dependencies are not touched, as
DataDog/tracing dependencies still give trouble.
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>

Don't add pods to our internal cache that are being deleted. This saves
a field in the struct as well.

Add (extra) comments about adding fields to the
object/{Pod,Service,Endpoint} structs.
Signed-off-by: Miek Gieben <miek@miek.nl>

General syntactic cleanup.

* make sure client CA and auth type are set if CA is explicitly specified.

added some simple tests to confirm the effect.

* test certificates (forgot to add them in the previous commit)

* made client auth policy configurable with new client_auth option.

README has been updated accordingly.

* fix editorial in README

* client-go 11.0.0

* Core moved to CoreV1

* Fix for #2842, instead of returning the first Pod, return the one which is Running

* a more memory efficient version of the fix, string -> bool

* fix with no extra fields in struct, return nil at Pod conversion if Pod is not Running

* let Kuberneretes filter for Running Pods using FieldSelector

* filter for Pods that are Running and Pending (implicit)

* Add server instance to the context in ServerTLS and ServerHTTPS

The problem with the current code is that there's no way to get the server instance inside a plugin.
Because of that "metrics" plugin sets empty "server" label for requests served over TLS or HTTPS.

* use s.Server instead of s

* Added server to the context of grpc requests

This fix:
1. Update dns to v1.1.12
2. Redirect dns v1.1.3 in caddy to v1.1.12 so that there is only one version of dns.
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>

Update shebangs for environmentally finding Bash -- Compatibility update to provide support for platforms that do not ship Bash in their /bin (#2841)

Signed-off-by: Yong Tang <yong.tang.github@outlook.com>

* pkg/log: fix data race on d

Wrap d in a mutex to prevent data race. This makes is slower, but this
is a debugging aid anyway. It's not used normally.
Signed-off-by: Miek Gieben <miek@miek.nl>

* Fix tests compilation
Signed-off-by: Miek Gieben <miek@miek.nl>

* Fix test compile
Signed-off-by: Miek Gieben <miek@miek.nl>

This fixes a data race on the listener(s) that get started in the
metrics plugins.

It also restore pkg/uniq to its former glory and removes and state being
carried in there; this means for metrics that registry.go was to
replicate that behavior *with* locking (as pkg/uniq doesn't do, or need
that).

Also renamed uniqAddr to just u, to make it slightly shorter.
Signed-off-by: Miek Gieben <miek@miek.nl>

Reset the buf otherwise we're not checking the new value.
Signed-off-by: Miek Gieben <miek@miek.nl>

Fix metrics endpoint on a failed reload, follows the same lines as the
previous PRs, see for e.g. 076b8d4f. Test with a Corefile with 2 server
blocks and metrics enabled and then introducing a syntax error:

~~~
[ERROR] Restart failed: Corefile:5 - Error during parsing: Unknown directive 'jfkdjk'
[ERROR] SIGUSR1: starting with listener file descriptors: Corefile:5 - Error during parsing: Unknown directive 'jfkdjk'
~~~

And then curl-ing the metrics endpoint.

See #2659 and as this is the last one.

Fixes: #2659

Getting this all right turns out to be tricky, also it's not easy
testable which is something I should fix.
Signed-off-by: Miek Gieben <miek@miek.nl>

Signed-off-by: Yong Tang <yong.tang.github@outlook.com>

This has somehow survived; the docs still used Middleware instead of
Plugins.
Signed-off-by: Miek Gieben <miek@miek.nl>

Update this file, give Readiness its own section and remove the talk
about the *reverse* plugin as it does not exist in the main tree
anymore.
Signed-off-by: Miek Gieben <miek@miek.nl>

Add OnReStartFailed which makes the health plugin stay up if the
Corefile is corrupt and we revert to the previous version.

Also needs a fix for the channel handling

See #2659

Testing it will log the following when restarting with a corrupted
Corefile

~~~
2019-05-04T18:01:59.431Z [INFO] linux/amd64, go1.12.4,
CoreDNS-1.5.0
linux/amd64, go1.12.4,
[INFO] SIGUSR1: Reloading
[INFO] Reloading
[ERROR] Restart failed: Corefile:5 - Error during parsing: Unknown directive 'bdhfhdhj'
[ERROR] SIGUSR1: starting with listener file descriptors: Corefile:5 - Error during parsing: Unknown directive 'bdhfhdhj'
~~~

After which the curl still works.

This also needed a change to reset the channel used for the metrics
go-routine which gets closed on shutdown, otherwise you'll see:

~~~
^C[INFO] SIGINT: Shutting down
panic: close of closed channel

goroutine 90 [running]:
github.com/coredns/coredns/plugin/health.(*health).OnFinalShutdown(0xc000089bc0, 0xc000063d88, 0x4afe6d)
~~~
Signed-off-by: Miek Gieben <miek@miek.nl>

Small, trivial cleanup: got triggered because I saw a comment on how
health plugins polls other plugins which isn't true.

* Remove useless newHealth function
* healthParse -> parse
* Remove useless constants

Net deletion of code.
Signed-off-by: Miek Gieben <miek@miek.nl>