From 1b0e7df966c95bfc0139cdaca488deb2c375a72c Mon Sep 17 00:00:00 2001 From: stack72 Date: Fri, 22 Jan 2021 22:31:41 +0000 Subject: [PATCH] Adding --show-secrets to pulumi stack output in the READMEs due to proliferating secrets in outputs --- aws-cs-eks/README.md | 2 +- aws-go-eks/README.md | 2 +- aws-ts-eks-distro/README.md | 2 +- aws-ts-eks-hello-world/README.md | 2 +- aws-ts-eks/README.md | 2 +- azure-cs-aks-private-container-registry/README.md | 2 +- azure-cs-aks/README.md | 2 +- azure-fs-aks/Makefile | 2 +- azure-fs-aks/README.md | 2 +- azure-go-aks/README.md | 2 +- azure-nextgen-cs-aks/README.md | 2 +- azure-nextgen-go-aks/README.md | 2 +- azure-nextgen-py-aks/README.md | 2 +- azure-nextgen-ts-aks/README.md | 2 +- azure-py-aks/README.md | 2 +- azure-ts-aks-helm/README.md | 2 +- azure-ts-aks-keda/README.md | 2 +- azure-ts-aks-mean/index.ts | 2 +- azure-ts-aks-with-diagnostics/README.md | 2 +- digitalocean-py-k8s/README.md | 2 +- digitalocean-ts-k8s/README.md | 2 +- gcp-cs-gke/README.md | 2 +- gcp-go-gke/README.md | 2 +- gcp-py-gke/README.md | 2 +- gcp-ts-gke-hello-world/README.md | 2 +- gcp-ts-gke-serviceaccount/README.md | 2 +- gcp-ts-gke/README.md | 2 +- gcp-ts-k8s-ruby-on-rails-postgresql/scripts/migrate.sh | 2 +- gcp-ts-k8s-ruby-on-rails-postgresql/scripts/setup.sh | 2 +- 29 files changed, 29 insertions(+), 29 deletions(-) diff --git a/aws-cs-eks/README.md b/aws-cs-eks/README.md index a6e3b1006..9e094375d 100644 --- 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 index e1f9f457e..c895b919e 100644 --- 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 index a8d4e82f9..b38eb6d8f 100644 --- 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 index eb522f0c5..19b6e4e76 100755 --- 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 index 286371b93..e6bcbe302 100755 --- 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 index 34e99ecc3..31124e944 100644 --- 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 index f9b79fd50..0df07c9e9 100644 --- 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 index 8cda5d2be..11b28e473 100644 --- 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 index add318351..00d9dbd0f 100644 --- 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 index f3c4c4235..9823263a4 100644 --- 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 index 23ee59fbe..2e490b9e2 100644 --- 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 index 8770b1f4a..defebaec5 100644 --- 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 index afd1ff2f1..19cc8a112 100644 --- 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 index f3e063c99..ba1fb35f1 100644 --- 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 index f9b5e76b4..e941b915f 100644 --- 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 index fa2ee8ebb..5a4bf93a9 100644 --- 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 index fd6d8d116..e52b9df40 100644 --- 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 index 8d3ed6738..40287f1f7 100644 --- 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 index f3f3b1bcc..14b4a5292 100644 --- 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 index 92a9718b9..c2bfec168 100644 --- 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 index 19a3bc22a..9b39f075d 100644 --- 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 index c450cd31e..d00ddd0fa 100644 --- 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 index f0a7efd6a..edfeefb3d 100644 --- 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 index 830d5edfc..9c70c1f97 100644 --- 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 index 685022830..83a72a4cc 100644 --- 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 index 2513d57c9..83c06ea87 100644 --- 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 index c8b5c3b3c..61492cac2 100644 --- 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 index d6bfe0824..e0a26ab17 100755 --- 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 index b3bc38aa6..a476cb02d 100755 --- 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