0.6.0

• routes tests are flaky
• Release notes for app-sd-release are populated with compatible versions
• ship what should be blocked on perf tests in SD pipeline
• Log when marking routes as stale
• Use cats-master in ushanka task
• fix app-sd acceptance tests
• cf-app-sd-release shipit does not correctly tag the final release
• stop using skip-ssl-validation in cf-app smoke tests
• Example app modifications
• CAT for ASGs applying to tasks
• use latest capi release
• Update to go 1.10
• Stop using the cats-concourse-task repo
• update branch pipelines for changes in cf-concourse-deployment-tasks
• cloudfoundry/cf-networking-release #36: Allowing networking tests to run in parallel with CF acceptance tests
• Add fast fail to shipit cf-app-sd release
• Run route integrity tests in our pipeline
  Tested with CAPI: 1.52.0, BOSH DNS: 1.3.0, Diego: 2.2.0

0.5.0

The primary change in this release a new flag to disable the functionality for cf-app-sd-release through a manifest property.

Stories

• appGUID.apps.internal routes are no longer generated
• cloudfoundry/cf-app-sd-release #4: error: lookup sql-db.service.cf.internal on 169.254.0.2:53: no such host
• cloudfoundry/cf-app-sd-release #5: Bosh Lite script: route doesn't exist on my Ubuntu machine
• Refactor and update docs to show metrics and tests for service discovery

0.4.0

• A CF operator should be able to add service discovery to cf-deployment
• A CF operator should be able to specify a staleness threshold for SD pruning
• A CF operator should be able to specify an interval for SD pruning
• At boot time, SDC should not respond to requests until it has received a full set of NATS messages
• Dont use capi-latest opsfile in ci
• ship a cf-app-sd version
• Pin to newest cf-deployment-concourse task release
• SDC should return a set of IPs in random order

0.3.0

v0.3.0

Release v0.3.0

0.2.0

v0.2.0

Release v0.2.0

0.1.0

v0.1.0

Release v0.1.0