1. 15 Jun, 2018 1 commit
  2. 06 Jun, 2018 1 commit
  3. 16 May, 2018 1 commit
  4. 23 Apr, 2018 2 commits
  5. 19 Apr, 2018 1 commit
  6. 18 Apr, 2018 1 commit
  7. 04 Apr, 2018 3 commits
  8. 13 Mar, 2018 1 commit
  9. 27 Feb, 2018 1 commit
  10. 22 Feb, 2018 1 commit
  11. 21 Feb, 2018 4 commits
    • Till Klocke's avatar
      Implementation of multiple targets based on PR #404 and #396 (#418) · 5d548496
      Till Klocke authored
      * 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 here is unnecessary complicated and doesn't deliver enough convenience
      
      * Reverted ConflictResolver to the original one. There is some discussing to do what the best way is to handle conflicts
      
      * Added missing documenting comment to IsLess of Targets
      
      * Added documenting comments to Targets,Targets.Same and NewTargets to clarify their intention and usage
      
      * Service source now also generates endpoints with multiple targets
      
      * Service and Ingress source now sort all Targets for every Endpoint to make order of Targets predictable
      
      * Endpoints generated by the Google Cloud DNS provider now also have sorted Targets to make order of Targets predictable
      
      * Modified provider dyn to be able to compile with multi target changes
      
      * Fixed small nitpicks, so my code is acceptable
      
      * Fixed merge method after updating to new Targets. Replacing '!=' with .Same of course needs a boolean negation
      
      * Tests for dyn provider now also use the new Targets instead of Target
      
      * Simplified extractServiceIps as implied by linki to make it more readable
      
      * ref: change service ClusterIP retrieval again
      
      * Added entry to CHANGELOG.md describing the new features contained in this PR
      5d548496
    • Nick Jüttner's avatar
      DigitalOcean creates entries with host in them twice (#459) · f5b0d93e
      Nick Jüttner authored
      * DigitalOcean creates entries with host in them twice
      
      * Unit test
      
      * DigitalOcean creates entries with host in them twice (#459)
      
      * docs: cleanup changelog a little
      f5b0d93e
    • James Bowes's avatar
      Retrive all DNSimple response pages (#468) · 9bd5f060
      James Bowes authored
      * 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
      9bd5f060
    • jvassev's avatar
      Graceful handling of misconfigure password for dyn (#470) · 3293af66
      jvassev authored
      * 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
      3293af66
  12. 19 Feb, 2018 1 commit
    • jvassev's avatar
      Don't log passwords on start (#463) · 02f83397
      jvassev authored
      * 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
      02f83397
  13. 26 Jan, 2018 1 commit
  14. 08 Jan, 2018 1 commit
    • leigh schrandt's avatar
      Google Provider logging for misconfigured zones (#388) · 930c8d48
      leigh schrandt authored
      * 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
      930c8d48
  15. 05 Jan, 2018 1 commit
    • Corey O'Brien's avatar
      Update AWS private hosted zones in addition to public zone (#356) · 53011dc1
      Corey O'Brien authored
      * Update AWS private hosted zones in addition to public zone
      
      * Sort slices for consistent ordering in TestAWSSuitableZones
      
      * ref: use len to check for empty list of matched zones
      
      * feat: mention contributors in changelog
      
      * fix: move changelog entry to the unreleased section
      
      * fix: add one more missing attribution to the changelog
      53011dc1
  16. 20 Dec, 2017 1 commit
  17. 14 Dec, 2017 1 commit
    • Yerken's avatar
      Multi target plan ( Page Not Found ) (#404) · ec07f45c
      Yerken authored
      * Make suitableType() be Endpoint method
      
      With this change it becomes possible to work with endpoint
      of empty type in packages other than "provider". Also
      it seems logical for a smart property getter without side effects
      to be a method rather than a function in different package
      
      * Make plan computation work correctly with multi-target domains
      
      * fix drawing
      
      * drop comments
      
      * fix boilerplate header
      
      * fix comment
      
      * fix the bug with empty map
      
      * rework registry to support random lables
      
      *  serialize->serializeLabel function rename
      
      * golint for err variable naming
      
      * add additional test
      
      * add tests for current case where one resource can generate multiple endpoints
      
      * make labels have its own type, add serialization as a method
      
      * add comment for exported error
      
      * use greater rather than not equal zero
      
      * update changelog
      ec07f45c
  18. 22 Nov, 2017 1 commit
  19. 14 Nov, 2017 1 commit
  20. 09 Nov, 2017 1 commit
  21. 18 Oct, 2017 1 commit
    • Kévin Dunglas's avatar
      Cloudflare: Disable proxy mode for TXT and others (#361) · 19ab8cd6
      Kévin Dunglas authored
      * Cloudflare: Disable proxy mode for TXT and others
      
      * Improve code according to review
      
      * Add test
      
      * Disable proxy mode for wildcards
      
      * Fix review, add test
      
      * Move var
      
      * chore: fix some golang related stuff
      
      * chore: update changelog to reflect latest changes
      19ab8cd6
  22. 12 Oct, 2017 1 commit
  23. 11 Oct, 2017 2 commits
    • Kevin J. Qiu's avatar
      Allow specifying a custom TTL through annotation on Ingress or Service (#320) · 71723bdd
      Kevin J. Qiu authored
      * Add RecordTTL
      
      * Route53: test for custom TTL
      
      * Fix tests
      
      * Fix remaining tests
      
      * Add ttl when endpoint is created from ingress
      
      * Missed a word
      
      * Fix bad refactoring
      
      * Add ingress custom TTL test
      
      * gofmt
      
      * Satisfy go-lint
      
      * Unshadow `endpoint` in azure provider
      
      * Fix and add an output test
      
      * Add TTL for endpoints generated from service templates
      
      * Take TTL into account when generating update plan
      
      * Tests for TTL change impact on the plan
      
      * Refactor factory method name
      
      * Refactoring
      
      * Run gofmt
      
      * Make endpoint string format look like BIND config
      
      * Update plan and plan_test
      
      * Replace NewEndpointWithTTLValue with NewEndpointWithTTL in aws
      
      * Remove NewEndpointWithTTLValue func
      
      * Update references to TTL
      
      * Remove getTTLValue func
      
      * Handle merge conflict
      
      * Update tests
      
      * Update README, CHANGELOG and documentation
      
      * Run gofmt
      
      * Move getTTLFromAnnotations to a common file
      
      * Refactor getTTLFromAnnotations
      
      * Gofmt
      
      * Add tests for getTTLFromAnnotations
      
      * Trigger build
      
      * Add boilerplate header
      
      * Update README/CHANGELOG according to code review
      
      * Add ttl.md and link it from README
      
      * change CNAME string to endpoint.RecordTypeCNAME
      
      * fix test cases with AWS ALIAS records, these do not behave different in these tests
      71723bdd
    • jose5918's avatar
      Adds Dnsimple as new provider (#224) · 09c35b67
      jose5918 authored
      * Adds Dnsimple as a provider
      
      * chore(vendor): remove vendor for smaller diff
      
      * fix(config): make dnsimple selectable via flags
      
      * Fix delete and update
      
      * Dnsimple testify mock tests
      
      * remove leaked file
      
      * Move and simplify mock functions
      
      * chore: use lowercase for logrus repository
      
      * chore: update dependencies using glide
      
      * chore: vendor dnsimple-go package
      
      * ref: isolate suitable type in source package
      
      * add support for DNSimple, thx @jose5918 :D
      09c35b67
  24. 22 Sep, 2017 1 commit
  25. 17 Aug, 2017 3 commits
    • Henning Jacobs's avatar
      a7a1cbc1
    • Justin Nauman's avatar
      ClusterIp Service support (#278) · 9b32e162
      Justin Nauman authored
      * ClusterIP service support
      
      - First pass at addresssing #187 by allowing services with type ClusterIP to be directly supported
      
      * Getting existing tests to pass
      
      * Adjusting formatting for gofmt/govet
      
      * Adding in guard logic around publishing of ClusterIP sources
      
      * Addressing PR feedback
      
      * Adding in CHANGELOG entry
      
      * Adding in Headless service test
      9b32e162
    • Clayton O'Neill's avatar
      Ingress target annotation should set, not append (#318) · ea4cbfe8
      Clayton O'Neill authored
      If the user has specified a target for the ingress, treat that as
      overriding any endpoints already set on the ingress, even if that list
      is not empty.  This allows overriding the IP address or hostname set
      when using a service like kube-keepalived-vip.
      ea4cbfe8
  26. 03 Aug, 2017 1 commit
  27. 31 Jul, 2017 1 commit
  28. 24 Jul, 2017 1 commit
  29. 21 Jul, 2017 1 commit
  30. 04 Jul, 2017 1 commit
  31. 29 Jun, 2017 1 commit
    • Nils Juenemann's avatar
      Support for multiple domains within --domain-filter (#252) · 73d39796
      Nils Juenemann authored
      * Support for multiple domains within --domain-filter
      
      The parameter accepts a comma separated list of domains with or without trailing dot. Example: --domain-filter="example.org, company.test.,staging.com". Closes #247 and #229
      
      * Add boilerplate header
      
      * Add documentation for methods and structs
      
      * use StringsVar for the domain-filter flag
      
      * go fmt
      
      * Remove camel case from tests
      
      * Revert changes in README.md
      
      * Move DomainFilter to provider package
      
      * Make a new slice and copy elements to it
      
      * Update CHANGELOG.md
      
      * docs: change minor spelling mistake
      73d39796