Signed-off-by: njuettner <nick@zalando.de>

Signed-off-by: Nick Jüttner <nick@zalando.de>

Signed-off-by: njuettner <nick@zalando.de>

Updating CHANGELOG.md with 'Add aws evaluate target health flag' PR.

* Create `NewAWSProvider` with `AWSConfig` struct

Rather than calling `NewAWSProvider` with a list of objects, you will
now call it using a new `AWSConfig` struct. This allows for clearer
declarations of variables which becomes even  more important as more
variables are added.

* Add `aws-max-change-count` flag

Adding a new `aws-max-change-count` flag to override the default max
change count on the aws provider.

Included updated tests with a new `defaultMaxChangeCount` constant and
tests for setting the value as a flag and as an environment variable.

* Update CHANGELOG.md

Updating CHANGELOG.md with 'Add aws max change count flag' PR.

* Add recent changes to the changelog
* Update version in docs
Signed-off-by: Nick Jüttner <nick@zalando.de>

* fix(google): correctly filter records that don't match all filters

* update changelog with the filters fix

* fix(google): add test to ensure domain filter works

* Add a flag that allows FQDN and Annotations to combine

Old behaviour is kept by default, a new flag is introduced to combine instead of overwrite

Fixes #218

* docs: add fqdn template combine to changelog

* for headless services use podip instead of hostip

* docs: add hostIP to podIP switch to changelog

* Support a comma separated list for the FQDN template

* Add documentation for comma separated FQDN templates

* chore: add multiple fqdn templates to changelog

* Auto-detect google-project if provider is Google and no project is supplied.

* Add changelog entry.

* Add custom TTL support for DNSimple

* chore: add changelog entry

* Fix docker build and delete vendor files which were not deleted

* Fix docker build and delete vendor files which were not deleted

* Add me as a owner

* Fix docker build and delete vendor files which were not deleted

* Endpoint.Target is now Endpoint.Targets. This is its own type representing mutliple targets for a single DNS name while adding some convenience for sorting and comparing

* Made everything compile and tests run through with the new Endpoint.Targets

* The ingress source can now properly handle multiple target ips per host

* Added custom conflict resolver, to better understand how conflict resolution has to work for me

* My custom conflict resolver behaves a bit different than the PerResource resolver, therefore I needed to modify the expected test result

Removed unnecessary FIXME

* The ingress source now creates CNAME endpoints with multiple targets to let the DNS provider decide how to handle multiple CNAME targets. This could be interesting for weighted targets etc.

* Adopted the expected results to the new way we create endpoints for CNAMEs

* Removed Add method from Targets since manipulating the slice through h...

* DigitalOcean creates entries with host in them twice

* Unit test

* DigitalOcean creates entries with host in them twice (#459)

* docs: cleanup changelog a little

* Retrive all DNSimple response pages

The DNSimple API is paginated. Retrive all pages when requesting zones
and records, so that none are skipped.

When querying for a single record, ask for it by name. That way, there
will be fewer pages to iterate through.

* docs: add pagination support for dnsimple to changelog

* Graceful handling of misconfigure password for dyn

If a bad password is given for provider "dyn" then the next
login attempt is at least 30minutes apart. This prevents an
account from being suspended.

Improve validation of flags for dyn provider. Add test for
ValidateConfig() and Config.String()

Also add --dyn-min-ttl option which sets the lower limit
of a record's TTL. Ignored if 0 (the default).

* docs: add graceful handling of misconfiguration to changelog

* Don't log passwords on start

The two passwords configurable as flags (for infoblox and dyn) are
masked now and not logged.

* docs: add masking sensitive data in logs to changelog

* provider=google: Improve Logging / Filter Endpoints

1. move dry-run exit after `separateChange()`
2. log records after `separateChange()`
3. make `newRecords()` a method of `GoogleProvider` — use `domainFilter.Match()` foreach `endpoint.DNSName`
   ^ without this, non-relevant endpoints show up in the warnings for “No matching zone”

* provider=google: Add tests for domainFilter

- new test: `TestGoogleRecordsFilter`
- add no matching zone and filtered record to `TestGoogleApplyChanges`
- allow `setupGoogleRecords` to createRecords without validateEndpoints

* provider=google: Improve zone-matching logs

- Add `DomainFilter.isConfigured()`
- Conditionally log zone matching for the user based off of `DomainFilter.isConfigured()`
- Rename `provider.newRecords()` to `provider.newFilteredRecords`

* fix: ensure that our setup methods are correct by keeping the tests