Use `pulumi.Config()` instead of `pulumi.Config("whatever")`
Fixes
MODIFY
kubernetes-ts-configmap-rollout/README.md
kubernetes-ts-configmap-rollout/README.md
@@ -32,7 +32,7 @@ a `Service` of type `LoadBalancer`. Since minikube does not support
all you need to do is to tell it whether you're deploying to minikube:
```sh
-pulumi config set rolloutTest:isMinikube <value>
+pulumi config set isMinikube <value>
```
Perform the deployment:
@@ -66,12 +66,10 @@ and `grep` to retrieve the `<title>` of the site the proxy points at.
$ curl -sL $(pulumi stack output frontendIp):80 | grep -C 1 "<title>"
<title>Pulumi. Serverless // Containers // Infrastructure // Cloud // DevOps</title>
-
```
Now, open `default.conf` and change `.node.server` and `.server.location.proxy_set_header` to point
-at `google.com`. If you're on macOS you can run `sed -i bak "s/pulumi.github.io/google.com/g"
-default.conf`
+at `google.com`. If you're on macOS you can run `sed -i bak "s/pulumi.github.io/google.com/g" default.conf`
The result should look like this:
@@ -141,7 +139,7 @@ Permalink: https://app.pulumi.com/hausdorff/configmap-rollout-dev/updates/13
Now, if we `curl` the IP address once more, we see that it points at google.com!
-> *Note*: minikube does not support type `LoadBalancer`; if you are deploying to minikube, make sure
+> _Note_: minikube does not support type `LoadBalancer`; if you are deploying to minikube, make sure
> to run `kubectl port-forward svc/frontend 8080:80` to forward the cluster port to the local
> machine and access the service via `localhost:8080`.

MODIFY
kubernetes-ts-configmap-rollout/index.ts
kubernetes-ts-configmap-rollout/index.ts
@@ -4,7 +4,7 @@ import * as k8s from "@pulumi/kubernetes";
// Minikube does not implement services of type `LoadBalancer`; require the user to specify if we're
// running on minikube, and if so, create only services of type ClusterIP.
-let config = new pulumi.Config("rolloutTest");
+let config = new pulumi.Config();
let isMinikube = config.require("isMinikube");
const appName = "nginx";

MODIFY
kubernetes-ts-exposed-deployment/README.md
kubernetes-ts-exposed-deployment/README.md
@@ -35,7 +35,7 @@ This example will attempt to expose the `nginx` deployment Internet with a `Serv
type `ClusterIP` instead; all you need to do is to tell it whether you're deploying to minikube:
```sh
-pulumi config set nginx:isMinikube <value>
+pulumi config set isMinikube <value>
```
Perform the deployment:
@@ -70,7 +70,7 @@ We can see here in the `---outputs:---` section that Wordpress was allocated a p
case `35.226.79.225`. It is exported with a stack output variable, `frontendIp`. We can use `curl`
and `grep` to retrieve the `<title>` of the site the proxy points at.
-> *Note*: minikube does not support type `LoadBalancer`; if you are deploying to minikube, make sure
+> _Note_: minikube does not support type `LoadBalancer`; if you are deploying to minikube, make sure
> to run `kubectl port-forward svc/frontend 8080:80` to forward the cluster port to the local
> machine and access the service via `localhost:8080`.

MODIFY
kubernetes-ts-exposed-deployment/index.ts
kubernetes-ts-exposed-deployment/index.ts
@@ -3,7 +3,7 @@ import * as k8s from "@pulumi/kubernetes";
// Minikube does not implement services of type `LoadBalancer`; require the user to specify if we're
// running on minikube, and if so, create only services of type ClusterIP.
-let config = new pulumi.Config("nginx");
+let config = new pulumi.Config();
let isMinikube = config.require("isMinikube");
// nginx container, replicated 1 time.

MODIFY
kubernetes-ts-guestbook/simple/README.md
kubernetes-ts-guestbook/simple/README.md
@@ -30,7 +30,7 @@ already knows to use type `ClusterIP` instead; all you need to do is to tell it
deploying to minikube:
```sh
-pulumi config set guestbook:isMinikube <value>
+pulumi config set isMinikube <value>
```
Perform the deployment:

MODIFY
kubernetes-ts-guestbook/simple/index.ts
kubernetes-ts-guestbook/simple/index.ts
@@ -5,7 +5,7 @@ import * as k8s from "@pulumi/kubernetes";
// Minikube does not implement services of type `LoadBalancer`; require the user to specify if we're
// running on minikube, and if so, create only services of type ClusterIP.
-let config = new pulumi.Config("guestbook");
+let config = new pulumi.Config();
let isMinikube = config.getBoolean("isMinikube");
//

MODIFY
kubernetes-ts-helm-wordpress/index.ts
kubernetes-ts-helm-wordpress/index.ts
@@ -3,7 +3,7 @@ import * as k8s from "@pulumi/kubernetes";
// Minikube does not implement services of type `LoadBalancer`; require the user to specify if we're
// running on minikube, and if so, create only services of type ClusterIP.
-let config = new pulumi.Config("wordpress");
+let config = new pulumi.Config();
if (config.require("isMinikube") === "true") {
throw new Error("This example does not yet support minikube");
}

MODIFY
kubernetes-ts-jenkins/README.md
kubernetes-ts-jenkins/README.md
@@ -8,7 +8,7 @@ Kubernetes cluster using Pulumi and `@pulumi/kubernetes`.
Follow the steps in [Pulumi Installation and Setup](https://pulumi.io/install/) and [Configuring Pulumi
Kubernetes](https://pulumi.io/reference/kubernetes.html#configuration) to get setup with Pulumi and Kubernetes.
-> *Note*: The code in this repo assumes you are deploying to a cluster that supports the
+> _Note_: The code in this repo assumes you are deploying to a cluster that supports the
> [`LoadBalancer`](https://kubernetes.io/docs/concepts/services-networking/service/#type-loadbalancer) service type.
> This includes most cloud providers as well as [Docker for Mac Edge w/
> Kubernetes](https://docs.docker.com/docker-for-mac/kubernetes/). If not (for example if you are targeting `minikube`
@@ -34,8 +34,8 @@ Create configuration keys for the root username and password for the Jenkins ins
about to create:
```
-$ pulumi config set jenkins:username <your desired username>
-$ pulumi config set jenkins:password <your desired password> --secret
+$ pulumi config set username <your desired username>
+$ pulumi config set password <your desired password> --secret
```
Preview the deployment of the application:
@@ -95,7 +95,7 @@ The Jenkins instance we just deployed is reachable through port 80 of the extern
visit `http://35.230.56.127/jenkins/login` in a Web browser to begin the first-install flow for your new Jenkins instance.
You can use the username and password that you saved in your Pulumi config to log in to your new Jenkins instance.
-> *Note*: If you are deploying to a cluster that does not support `type: "LoadBalancer"`, and deployed the example using
+> _Note_: If you are deploying to a cluster that does not support `type: "LoadBalancer"`, and deployed the example using
> `type: "ClusterIP"` instead, run `kubectl port-forward svc/jenkins 8080:80` to forward the cluster port to the local
> machine and access the service via `localhost:8080`.

MODIFY
kubernetes-ts-jenkins/index.ts
kubernetes-ts-jenkins/index.ts
@@ -3,7 +3,7 @@ import * as jenkins from "./jenkins";
// Minikube does not implement services of type `LoadBalancer`; require the user to specify if we're
// running on minikube, and if so, create only services of type ClusterIP.
-const config = new pulumi.Config("jenkins");
+const config = new pulumi.Config();
if (config.require("isMinikube") === "true") {
throw new Error("This example does not yet support minikube");
}

MODIFY
kubernetes-ts-sock-shop/index.ts
kubernetes-ts-sock-shop/index.ts
@@ -5,7 +5,7 @@ import * as k8s from "@pulumi/kubernetes";
// Minikube does not implement services of type `LoadBalancer`; require the user to specify if we're
// running on minikube, and if so, create only services of type ClusterIP.
-const config = new pulumi.Config("sockshop");
+const config = new pulumi.Config();
if (config.require("isMinikube") === "true") {
throw new Error("This example does not yet support minikube");
}

Use `pulumi.Config()` instead of `pulumi.Config("whatever")`

Fixes #128.