luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Generalize base64 command usage in docs 

The base64 CLI utility has two different short flag arguments for decode
depending on the platform: -D and -d.

Previously, the docs used the -D flag exclusively with the base64 utility.
Luckily, the long form of the flag is the same across platforms: --decode.

All uses of the base64 -D flag have been replaced with --decode.
This commit is contained in:
Jared Kirschner 2021-07-28 11:40:35 -04:00
parent f39d36d346
commit 6bcc864819
5 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/content/docs/k8s/connect/terminating-gateways.mdx
View File

@ -69,7 +69,7 @@ $ export CONSUL_HTTP_SSL_VERIFY=false
If ACLs are enabled also set:
```shell-session
$ export CONSUL_HTTP_TOKEN=$(kubectl get secret consul-bootstrap-acl-token -o jsonpath={.data.token} | base64 -D)
$ export CONSUL_HTTP_TOKEN=$(kubectl get secret consul-bootstrap-acl-token -o jsonpath={.data.token} | base64 --decode)
```
## Register external services with Consul

2
website/content/docs/k8s/installation/deployment-configurations/consul-enterprise.mdx
View File

@ -104,7 +104,7 @@ Then you have likely enabled ACLs. You need to specify your ACL token when
running the `license get` command. First, assign the ACL token to the `CONSUL_HTTP_TOKEN` environment variable:
```shell-session
$ export CONSUL_HTTP_TOKEN=$(kubectl get secrets/hashicorp-consul-bootstrap-acl-token --template={{.data.token}} | base64 -D)
$ export CONSUL_HTTP_TOKEN=$(kubectl get secrets/hashicorp-consul-bootstrap-acl-token --template={{.data.token}} | base64 --decode)
```
Now the token will be used when running Consul commands:

2
website/content/docs/k8s/installation/install.mdx
View File

@ -158,7 +158,7 @@ to see all resources and make modifications.
To retrieve the bootstrap token that has full permissions, run:
```shell-session
$ kubectl get secrets/consul-bootstrap-acl-token --template={{.data.token}} | base64 -D
$ kubectl get secrets/consul-bootstrap-acl-token --template={{.data.token}} | base64 --decode
e7924dd1-dc3f-f644-da54-81a73ba0a178%
```

4
website/content/docs/k8s/installation/multi-cluster/vms-and-kubernetes.mdx
View File

@ -36,14 +36,14 @@ The following sections detail how to export this data.
```sh
kubectl get secrets/consul-ca-cert --template='{{index .data "tls.crt" }}' |
base64 -D > consul-agent-ca.pem
base64 --decode > consul-agent-ca.pem
```
1. And the certificate authority signing key:
```sh
kubectl get secrets/consul-ca-key --template='{{index .data "tls.key" }}' |
base64 -D > consul-agent-ca-key.pem
base64 --decode > consul-agent-ca-key.pem
```
1. With the `consul-agent-ca.pem` and `consul-agent-ca-key.pem` files you can

2
website/content/docs/security/acl/auth-methods/oidc.mdx
View File

@ -201,7 +201,7 @@ be tricky to debug why things aren't working. Some tips for setting up OIDC:
request to obtain a JWT that you can inspect. An example of how to decode the
JWT (in this case located in the `access_token` field of a JSON response):
cat jwt.json | jq -r .access_token | cut -d. -f2 | base64 -D
cat jwt.json | jq -r .access_token | cut -d. -f2 | base64 --decode
- The [`VerboseOIDCLogging`](#verboseoidclogging) option is available which
will log the received OIDC token if debug level logging is enabled. This can