Co-authored-by: Raffaele Di Fazio <raffo@github.com>

The new BlueCat provider uses the BlueCat API Gateway(REST API). Not
the legacy XML based BlueCat API.

https://github.com/bluecatlabs/gateway-workflows

Currently, the minimum delay between 2 kubernetes events handling is
hard-coded to 5s.

This may cause higher synchronization rates and higher DNS provider API
calls when handling an important number of kubernetes events at once.

Give the opportunity to configure this delay so service owners can
define the acceptable thresholds on their side

Co-authored-by: Nick Jüttner <nick@juni.io>

* adds flag to opt in for NS records management
Signed-off-by: Raffaele Di Fazio <difazio.raffaele@gmail.com>

* go fmt
Signed-off-by: Raffaele Di Fazio <difazio.raffaele@gmail.com>

* goimports
Signed-off-by: Raffaele Di Fazio <difazio.raffaele@gmail.com>

* fix more tests
Signed-off-by: Raffaele Di Fazio <difazio.raffaele@gmail.com>

* go fmt again
Signed-off-by: Raffaele Di Fazio <difazio.raffaele@gmail.com>

* fix test
Signed-off-by: Raffaele Di Fazio <difazio.raffaele@gmail.com>

* more tests
Signed-off-by: Raffaele Di Fazio <difazio.raffaele@gmail.com>

* make ordering of managed records consistent
Signed-off-by: Raffaele Di Fazio <difazio.raffaele@gmail.com>

* fix flag
Signed-off-by: Raffaele Di Fazio <difazio.raffaele@gmail.com>

First commit

Add common config to be shared by both azure and azure-private-dns providers
Update tests & docs

refactor: remove dns api logic and use dns api library
enhancement: add additional args for auth credential retieval
cleanup: simplify, organize processing logic
test: update automation and validate

* Added label filter for source CRD

* Fixed bug with labels and added tests for source CRD

* Fixed formating

* Update source/crd_test.go
Co-authored-by: Vinny Sabatini <vincent.sabatini@gmail.com>
Co-authored-by: Vinny Sabatini <vincent.sabatini@gmail.com>

When it syncs AWS DNS with k8s cluster content (at `--interval`), external-dns submits two distinct Route53 API calls:
* to fetch available zones (eg. for tag based zones discovery, or when zones are created after exernal-dns started),
* to fetch relevant zones' resource records.

Each call taxes the Route53 APIs calls budget (5 API calls per second per AWS account/region hard limit), increasing the probability of being throttled.
Changing synchronization interval would mitigate those calls' impact, but at the cost of keeping stale records for a longer time.

For most practical uses cases, zones list aren't expected to change frequently.
Even less so when external-dns is provided an explicit, static zones set (`--zone-id-filter` rather than `--aws-zone-tags`).

Using a zones list cache halves the number of Route53 read API calls.

Signed-off-by: Patrik Cyvoct <patrik@ptrk.io>

Support wildcard records - Optional ability to replace the asterisk in generated registry TXT records with another string

* intial removal of inappropriate terminology
Signed-off-by: Raffaele Di Fazio <raffo@github.com>

* removed other occurrences
Signed-off-by: Raffaele Di Fazio <raffo@github.com>

* gofmt
Signed-off-by: Raffaele Di Fazio <raffo@github.com>

* addresses comment
Signed-off-by: Raffaele Di Fazio <raffo@github.com>

* gofmt
Signed-off-by: Raffaele Di Fazio <raffo@github.com>

To run:

provide token HETZNER_TOKEN in ENV
set command line parameter --provider=hetzner

Signed-off-by: Raffaele Di Fazio <difazio.raffaele@gmail.com>

 - OVH Provider
 - Tests
 - Documentations

add documentation for kube-ingress-aws-controller and RouteGroup
Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>

This moves `domain_filter.go` to the `endpoint` package to make it
possible to filter and exclude record names in
`plan.filterRecordsForPlan()` so it does not have to be implemented in
every single provider.

Because some providers access `DomainFilter.filters` directly it had to
be exported.