doc: don't set ETCDCTL_API=3 in local_cluster guide
These docs are incorrectly saying that v2 is the default.
Note: v3 has been the default since
@@ -21,14 +21,7 @@ The running etcd member listens on `localhost:2379` for client requests.
Use `etcdctl` to interact with the running cluster:
-1. Configure the environment to have `ETCDCTL_API=3` so `etcdctl` uses the etcd API version 3 instead of defaulting to version 2.
-
- ```
- # use API version 3
- $ export ETCDCTL_API=3
- ```
-
-2. Store an example key-value pair in the cluster:
+1. Store an example key-value pair in the cluster:
```
$ ./etcdctl put foo bar
@@ -37,7 +30,7 @@ Use `etcdctl` to interact with the running cluster:
If OK is printed, storing key-value pair is successful.
-3. Retrieve the value of `foo`:
+2. Retrieve the value of `foo`:
```
$ ./etcdctl get foo
@@ -70,14 +63,7 @@ A `Procfile` at the base of the etcd git repository is provided to easily config
Use `etcdctl` to interact with the running cluster:
-1. Configure the environment to have `ETCDCTL_API=3` so `etcdctl` uses the etcd API version 3 instead of defaulting to version 2.
-
- ```
- # use API version 3
- $ export ETCDCTL_API=3
- ```
-
-2. Print the list of members:
+1. Print the list of members:
```
$ etcdctl --write-out=table --endpoints=localhost:2379 member list
@@ -94,7 +80,7 @@ Use `etcdctl` to interact with the running cluster:
+------------------+---------+--------+------------------------+------------------------+
```
-3. Store an example key-value pair in the cluster:
+2. Store an example key-value pair in the cluster:
```
$ etcdctl put foo bar
