Revision 8242049a339f36bab88a4dcc151e6b47e1c55e68 authored by fanmin shi on 29 December 2016, 22:37:25 UTC, committed by GitHub on 29 December 2016, 22:37:25 UTC
e2e: unset ETCDCTL_API env var before running e2e tests
2 parent s 734dd75 + b741452
Raw File
NEWS
etcd v3.0.15 (2016-11-11)
- fix cancel watch request with wrong range end

etcd v3.0.14 (2016-11-04)
- v3 etcdctl migrate command now supports --no-ttl flag to discard keys on transform

etcd v3.0.13 (2016-10-24)

etcd v3.0.12 (2016-10-07)

etcd v3.0.11 (2016-10-07)
- server returns previous key-value (optional)
  - clientv3 WithPrevKV option
  - v3 etcdctl prev-kv flag

etcd v3.0.10 (2016-09-23)

etcd v3.0.9 (2016-09-15)
- warn on domain names on listen URLs (v3.2 will reject domain names)

etcd v3.0.8 (2016-09-09)
- allow only IP addresses in listen URLs (domain names are rejected)

etcd v3.0.7 (2016-08-31)
- SRV records only allow A records (RFC 2052)

etcd v3.0.6 (2016-08-19)

etcd v3.0.5 (2016-08-19)
- SRV records (e.g., infra1.example.com) must match the discovery domain
  (i.e., example.com) when using the default certificate authority.

etcd v3.0.4 (2016-07-27)
- v2 auth can now use common name from TLS certificate when --client-cert-auth is enabled
- v2 etcdctl ls command now supports --output=json
- Add /var/lib/etcd directory to etcd official Docker image

etcd v3.0.3 (2016-07-15)
- Revert Dockerfile to use CMD, instead of ENTRYPOINT, to support etcdctl run
- Docker commands for v3.0.2 won't work without specifying executable binary paths
- v3 etcdctl default endpoints are now 127.0.0.1:2379

etcd v3.0.2 (2016-07-08)
- Dockerfile uses ENTRYPOINT, instead of CMD, to run etcd without binary path specified

etcd v3.0.1 (2016-07-01)
back to top