Andrew Lytvynov 03064cfa96 etcd: don't confuse prefixes during migration ...

The prefix fetching logic has a bug: it treats everything starting with
`/teleport` as the legacy prefix data, even if it's `/teleport-foo/bar`.
This is an issue if user specifies `/teleport-foo` as their custom
prefix. Each restart will copy the data from `/teleport-foo/...` to
`/teleport-foo-foo/...`.

Set the legacy prefix const to `/teleport/` instead. This avoids
excessive copying during startup.

Prefixes can still be confused later on, with `Watch` and `GetRange`,
but this is harder to migrate with backwards-compatibility.

2020-09-14 21:26:36 +00:00

..

certs

Updating dependencies for etcd v3.3.15 (#2965)

2019-09-08 10:50:56 -07:00

.gitignore

Merge branch 'master' into ev/688

2017-01-16 00:59:28 -08:00

docker-compose.yml

Add clustered etcd docker-compose example

2018-08-27 13:54:41 -07:00

etcdctl.sh

etcd: don't confuse prefixes during migration

2020-09-14 21:26:36 +00:00

gen.py

Add clustered etcd docker-compose example

2018-08-27 13:54:41 -07:00

start-etcd-insecure.sh

Added 'insecure' flag to etcd config

2017-01-16 11:15:04 -08:00

start-etcd.sh

etcd: don't confuse prefixes during migration

2020-09-14 21:26:36 +00:00

start-teleport-insecure.sh

Added 'insecure' flag to etcd config

2017-01-16 11:15:04 -08:00

start-teleport.sh

Merge branch 'master' into ev/688

2017-01-16 00:59:28 -08:00

teleport-insecure-etcd.yaml

Added 'insecure' flag to etcd config

2017-01-16 11:15:04 -08:00

teleport.yaml

Finished cleaning up storage back-ends

2017-01-15 23:23:37 -08:00