Adding --show-secrets to pulumi stack output in the READMEs due to pr…

…oliferating secrets in outputs
dlactin · Jan 22, 2021 · 1b0e7df · 1b0e7df
1 parent 36c4760
commit 1b0e7df
Show file tree

Hide file tree

Showing 29 changed files with 29 additions and 29 deletions.
diff --git a/aws-cs-eks/README.md b/aws-cs-eks/README.md
@@ -39,7 +39,7 @@ After cloning this repo, run these commands from the working directory:
  be available as an output. You can save this kubeconfig to a file like so:
 
  ```bash
- $ pulumi stack output kubeconfig >kubeconfig.json
+ $ pulumi stack output kubeconfig --show-secrets >kubeconfig.json
  ```
 
  Once you have this file in hand, you can interact with your new cluster as usual via `kubectl`:

diff --git a/aws-go-eks/README.md b/aws-go-eks/README.md
@@ -39,7 +39,7 @@ After cloning this repo, run these commands from the working directory:
  be available as an output. You can save this kubeconfig to a file like so:
 
  ```bash
- $ pulumi stack output kubeconfig >kubeconfig.json
+ $ pulumi stack output kubeconfig --show-secrets >kubeconfig.json
  ```
 
  Once you have this file in hand, you can interact with your new cluster as usual via `kubectl`:

diff --git a/aws-ts-eks-distro/README.md b/aws-ts-eks-distro/README.md
@@ -48,7 +48,7 @@ After cloning this repo, from this working directory, run these commands:
  be available as an output. You can save this kubeconfig to a file like so:
 
  ```bash
- $ pulumi stack output kubeconfig >kubeconfig.json
+ $ pulumi stack output kubeconfig --show-secrets >kubeconfig.json
  ```
 
  Once you have this file in hand, you can interact with your new cluster as usual via `kubectl`:

diff --git a/aws-ts-eks-hello-world/README.md b/aws-ts-eks-hello-world/README.md
@@ -239,7 +239,7 @@ After cloning this repo, from this working directory, run these commands:
  stack output in the CLI, as Pulumi facilitates exporting these objects for us.
 
  ```bash
- $ pulumi stack output kubeconfig > kubeconfig
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig
  $ export KUBECONFIG=$PWD/kubeconfig
  $ export KUBERNETES_VERSION=1.11.5 && sudo curl -s -o /usr/local/bin/kubectl https://storage.googleapis.com/kubernetes-release/release/v${KUBERNETES_VERSION}/bin/linux/amd64/kubectl && sudo chmod +x /usr/local/bin/kubectl
 

diff --git a/aws-ts-eks/README.md b/aws-ts-eks/README.md
@@ -69,7 +69,7 @@ After cloning this repo, from this working directory, run these commands:
  be available as an output. You can save this kubeconfig to a file like so:
 
  ```bash
- $ pulumi stack output kubeconfig >kubeconfig.json
+ $ pulumi stack output kubeconfig --show-secrets >kubeconfig.json
  ```
 
  Once you have this file in hand, you can interact with your new cluster as usual via `kubectl`:

diff --git a/azure-cs-aks-private-container-registry/README.md b/azure-cs-aks-private-container-registry/README.md
@@ -51,7 +51,7 @@ To deploy your infrastructure, follow the below steps.
 5. After 10-15 minutes, your cluster will be ready, and the kubeconfig YAML you'll use to connect to the cluster will be available as an output. You can save this kubeconfig to a file like so:
 
  ```bash
- $ pulumi stack output KubeConfig > kubeconfig.yaml
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
  ```
 
  Once you have this file in hand, you can interact with your new cluster as usual via `kubectl`:

diff --git a/azure-cs-aks/README.md b/azure-cs-aks/README.md
@@ -45,7 +45,7 @@ To deploy your infrastructure, follow the below steps.
 5. After 10-15 minutes, your cluster will be ready, and the kubeconfig YAML you'll use to connect to the cluster will be available as an output. You can save this kubeconfig to a file like so:
 
  ```bash
- $ pulumi stack output KubeConfig > kubeconfig.yaml
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
  ```
 
  Once you have this file in hand, you can interact with your new cluster as usual via `kubectl`:

diff --git a/azure-fs-aks/Makefile b/azure-fs-aks/Makefile
@@ -17,7 +17,7 @@ deploy: build ## Deploy with -y
  pulumi up -y
 
 exportconfig: ## Exports the kubernetes config
- pulumi stack output kubeconfig > kubeconfig.yaml
+ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
 
 destroy: build ## Destroy with -y
  pulumi destroy -y

diff --git a/azure-fs-aks/README.md b/azure-fs-aks/README.md
@@ -66,7 +66,7 @@ $ pulumi up --yes
 This will prompt you to create a stack if you haven't done so already. When the deploy is ready you can export the kubernetes config with
 
 ```bash
-$ pulumi stack output kubeconfig > kubeconfig.yaml
+$ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
 ```
 
 and then test the deployment with

diff --git a/azure-go-aks/README.md b/azure-go-aks/README.md
@@ -50,7 +50,7 @@ To deploy your infrastructure, follow the below steps.
 1. After 10-15 minutes, your cluster will be ready, and the kubeconfig YAML you'll use to connect to the cluster will be available as an output. You can save this kubeconfig to a file like so:
 
  ```bash
- $ pulumi stack output kubeconfig > kubeconfig.yaml
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
  ```
 
  Once you have this file in hand, you can interact with your new cluster as usual via `kubectl`:

diff --git a/azure-nextgen-cs-aks/README.md b/azure-nextgen-cs-aks/README.md
@@ -44,7 +44,7 @@ After cloning this repo, from this working directory, run these commands:
 1. After 3-4 minutes, your cluster will be ready, and the kubeconfig YAML you'll use to connect to the cluster will be available as an output. You can save this kubeconfig to a file like so:
 
  ```bash
- $ pulumi stack output KubeConfig > kubeconfig.yaml
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
  ```
 
  Once you have this file in hand, you can interact with your new cluster as usual via `kubectl`:

diff --git a/azure-nextgen-go-aks/README.md b/azure-nextgen-go-aks/README.md
@@ -31,7 +31,7 @@ After cloning this repo, from this working directory, run these commands:
 1. After 3-4 minutes, your cluster will be ready, and the kubeconfig YAML you'll use to connect to the cluster will be available as an output. You can save this kubeconfig to a file like so:
 
  ```bash
- $ pulumi stack output kubeconfig > kubeconfig.yaml
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
  ```
 
  Once you have this file in hand, you can interact with your new cluster as usual via `kubectl`:

diff --git a/azure-nextgen-py-aks/README.md b/azure-nextgen-py-aks/README.md
@@ -43,7 +43,7 @@ After cloning this repo, from this working directory, run these commands:
 1. After 3-4 minutes, your cluster will be ready, and the kubeconfig YAML you'll use to connect to the cluster will be available as an output. You can save this kubeconfig to a file like so:
 
  ```bash
- $ pulumi stack output kubeconfig > kubeconfig.yaml
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
  ```
 
  Once you have this file in hand, you can interact with your new cluster as usual via `kubectl`:

diff --git a/azure-nextgen-ts-aks/README.md b/azure-nextgen-ts-aks/README.md
@@ -38,7 +38,7 @@ After cloning this repo, from this working directory, run these commands:
 1. After 3-4 minutes, your cluster will be ready, and the kubeconfig YAML you'll use to connect to the cluster will be available as an output. You can save this kubeconfig to a file like so:
 
  ```bash
- $ pulumi stack output kubeconfig > kubeconfig.yaml
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
  ```
 
  Once you have this file in hand, you can interact with your new cluster as usual via `kubectl`:

diff --git a/azure-py-aks/README.md b/azure-py-aks/README.md
@@ -60,7 +60,7 @@ After cloning this repo, from this working directory, run these commands:
 1. After 10-15 minutes, your cluster will be ready, and the kubeconfig YAML you'll use to connect to the cluster will be available as an output. You can save this kubeconfig to a file like so:
 
  ```bash
- $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
+ $ pulumi stack output kubeconfig --show-secrets --show-secrets > kubeconfig.yaml
  ```
 
  Once you have this file in hand, you can interact with your new cluster as usual via `kubectl`:

diff --git a/azure-ts-aks-helm/README.md b/azure-ts-aks-helm/README.md
@@ -61,7 +61,7 @@ After cloning this repo, `cd` into it and run these commands. A Kubernetes clust
  And you may also configure your `kubectl` client using the `kubeConfig` configuration:
 
  ```bash
- $ pulumi stack output kubeConfig > kubeconfig.yaml
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
  $ KUBECONFIG=./kubeconfig.yaml kubectl get service
  NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
  apache-apache LoadBalancer 10.0.125.196 40.76.52.208 80:32080/TCP,443:31419/TCP 9m

diff --git a/azure-ts-aks-keda/README.md b/azure-ts-aks-keda/README.md
@@ -61,7 +61,7 @@ After cloning this repo, `cd` into it and run these commands.
  Using these output variables, you may configure your `kubectl` client using the `kubeConfig` configuration:
 
  ```bash
- $ pulumi stack output kubeConfig > kubeconfig.yaml
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
  $ KUBECONFIG=./kubeconfig.yaml kubectl get deployment
  NAME READY UP-TO-DATE AVAILABLE AGE
  keda-edge 1/1 1 1 9m

diff --git a/azure-ts-aks-mean/index.ts b/azure-ts-aks-mean/index.ts
@@ -54,7 +54,7 @@ const node = new k8s.helm.v3.Chart(
 );
 
 // Export kubeconfig file, cluster name, and public IP address for Kubernetes application. These can
-// be accessed from the CLI, like: `pulumi stack output kubeconfig > kubeconfig.yaml`.
+// be accessed from the CLI, like: `pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml`.
 export const kubeconfig = k8sCluster.kubeConfigRaw;
 export const cluster = k8sCluster.name;
 export const frontendAddress = node

diff --git a/azure-ts-aks-with-diagnostics/README.md b/azure-ts-aks-with-diagnostics/README.md
@@ -43,7 +43,7 @@ After cloning this repo, `cd` into it and run these commands. A Kubernetes clust
  you may also configure your `kubectl` client using the `kubeconfig` configuration:
 
  ```bash
- $ pulumi stack output kubeconfig > kubeconfig.yaml
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
  $ kubectl get namespaces
  ....
  ```

diff --git a/digitalocean-py-k8s/README.md b/digitalocean-py-k8s/README.md
@@ -90,7 +90,7 @@ After cloning this repo, from this working directory, run these commands:```
  use that when running the `kubectl` command. For instance, this lists your pods:
 
  ```bash
- $ pulumi stack output kubeconfig > kubeconfig
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig
  $ KUBECONFIG=./kubeconfig kubectl get pods
  ```
 

diff --git a/digitalocean-ts-k8s/README.md b/digitalocean-ts-k8s/README.md
@@ -92,7 +92,7 @@ After cloning this repo, from this working directory, run these commands:
  use that when running the `kubectl` command. For instance, this lists your pods:
 
  ```bash
- $ pulumi stack output kubeconfig > kubeconfig
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig
  $ KUBECONFIG=./kubeconfig kubectl get pods
  ```
 

diff --git a/gcp-cs-gke/README.md b/gcp-cs-gke/README.md
@@ -101,7 +101,7 @@ After cloning this repo, from this working directory, run these commands:
  stack output in the CLI, as Pulumi facilitates exporting these objects for us.
 
  ```bash
- $ pulumi stack output KubeConfig > kubeconfig
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig
  $ export KUBECONFIG=$PWD/kubeconfig
 
  $ kubectl version

diff --git a/gcp-go-gke/README.md b/gcp-go-gke/README.md
@@ -102,7 +102,7 @@ After cloning this repo, from this working directory, run these commands:
  stack output in the CLI, as Pulumi facilitates exporting these objects for us.
 
  ```bash
- $ pulumi stack output kubeconfig > kubeconfig
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig
  $ export KUBECONFIG=$PWD/kubeconfig
 
  $ kubectl version

diff --git a/gcp-py-gke/README.md b/gcp-py-gke/README.md
@@ -83,7 +83,7 @@ After cloning this repo, `cd` into it and run these commands. A GKE Kubernetes c
  For instance:
 
  ```bash
- $ pulumi stack output kubeconfig > kubeconfig.yaml
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
  $ KUBECONFIG=./kubeconfig.yaml kubectl get po
  NAME READY STATUS RESTARTS AGE
  canary-n7wfhtrp-fdbfd897b-lrm58 1/1 Running 0 58s

diff --git a/gcp-ts-gke-hello-world/README.md b/gcp-ts-gke-hello-world/README.md
@@ -146,7 +146,7 @@ After cloning this repo, from this working directory, run these commands:
  stack output in the CLI, as Pulumi facilitates exporting these objects for us.
 
  ```bash
- $ pulumi stack output kubeconfig > kubeconfig
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig
  $ export KUBECONFIG=$PWD/kubeconfig
  $ export KUBERNETES_VERSION=1.11.6 && sudo curl -s -o /usr/local/bin/kubectl https://storage.googleapis.com/kubernetes-release/release/v${KUBERNETES_VERSION}/bin/linux/amd64/kubectl && sudo chmod +x /usr/local/bin/kubectl
 

diff --git a/gcp-ts-gke-serviceaccount/README.md b/gcp-ts-gke-serviceaccount/README.md
@@ -94,7 +94,7 @@ After cloning this repo, from this working directory, run these commands:
  stack output in the CLI, as Pulumi facilitates exporting these objects for us.
 
  ```bash
- $ pulumi stack output kubeconfig > kubeconfig
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig
  $ export KUBECONFIG=$PWD/kubeconfig
  $ kubectl version
  $ kubectl cluster-info

diff --git a/gcp-ts-gke/README.md b/gcp-ts-gke/README.md
@@ -82,7 +82,7 @@ After cloning this repo, `cd` into it and run these commands. A GKE Kubernetes c
  For instance:
 
  ```bash
- $ pulumi stack output kubeConfig > kubeconfig.yaml
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
  $ KUBECONFIG=./kubeconfig.yaml kubectl get po
  NAME READY STATUS RESTARTS AGE
  canary-n7wfhtrp-fdbfd897b-lrm58 1/1 Running 0 58s

diff --git a/gcp-ts-k8s-ruby-on-rails-postgresql/scripts/migrate.sh b/gcp-ts-k8s-ruby-on-rails-postgresql/scripts/migrate.sh
@@ -3,7 +3,7 @@
 set -ex
 
 export KUBECONFIG=$(mktemp)
-pulumi stack output kubeConfig > $KUBECONFIG
+pulumi stack output kubeconfig --show-secrets > $KUBECONFIG
 
 DEPLOYMENT=$(pulumi stack output appName)
 if [ -z "$DEPLOYMENT" ]; then

diff --git a/gcp-ts-k8s-ruby-on-rails-postgresql/scripts/setup.sh b/gcp-ts-k8s-ruby-on-rails-postgresql/scripts/setup.sh
@@ -3,7 +3,7 @@
 set -ex
 
 export KUBECONFIG=$(mktemp)
-pulumi stack output kubeConfig > $KUBECONFIG
+pulumi stack output kubeconfig --show-secrets > $KUBECONFIG
 
 DEPLOYMENT=$(pulumi stack output appName)
 if [ -z "$DEPLOYMENT" ]; then