From cbbe9da8902536fd17d0a4eb758d9cd09dea24dd Mon Sep 17 00:00:00 2001 From: Vico Chu <30412827+vicoooo26@users.noreply.github.com> Date: Wed, 11 Jan 2023 21:31:46 +0800 Subject: [PATCH] plugin/etcd: update documentation (#5847) Signed-off-by: Vico Chu Signed-off-by: Vico Chu --- plugin/etcd/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugin/etcd/README.md b/plugin/etcd/README.md index 6e83f2327..0c7f1ea33 100644 --- a/plugin/etcd/README.md +++ b/plugin/etcd/README.md @@ -62,7 +62,7 @@ The *etcd* plugin leverages directory structure to look for related entries. For an entry `/skydns/test/skydns/mx` would have entries like `/skydns/test/skydns/mx/a`, `/skydns/test/skydns/mx/b` and so on. Similarly a directory `/skydns/test/skydns/mx1` will have all `mx1` entries. Note this plugin will search through the entire (sub)tree for records. In case of the -first example, a query for `mx.skydns.text` will return both the contents of the `a` and `b` records. +first example, a query for `mx.skydns.test` will return both the contents of the `a` and `b` records. If the directory extends deeper those records are returned as well. With etcd3, support for [hierarchical keys are