~egtann/terrafirma

ef05efaf4cb4ae60b2a16869f7d9b655e188f497 — Evan Tann 21 days ago 73a67d1
fix readme issues
1 files changed, 7 insertions(+), 12 deletions(-)

M README.md
M README.md => README.md +7 -12
@@ 84,7 84,7 @@ deploy and the types of boxes you'll use. Here's an example:
		"debian": {
			"redis": 1
		}
	}
	},
	"providers": {
		"gcp:my-project:us-central1:us-central1-b": {
			"openbsd": {


@@ 110,8 110,8 @@ this:
#!/usr/bin/env bash
set -efux

TOKEN=$(gcloud auth print-access-token)
export TOKEN
GCP_TOKEN=$(gcloud auth print-access-token)
export GCP_TOKEN

# Plan the number of servers to be created and destroyed. This creates a
# tf_plan.json file which the remaining steps use.


@@ 135,16 135,11 @@ fi
terrafirma -i inventory > inventory.json

# Provision our servers using our usual deployment tools (cup, ansible, etc.).
up -t openbsd -c provision_openbsd
up -t debian  -c provision_debian
up -t 100.0.0.1 -c provision_openbsd
up -t 100.0.0.2 -c provision_debian

# Now we know our reverse proxy is sending traffic to these new boxes, so we
# can bring down our old ones and clean up any temporary files when we're done.
# First retrieve our full inventory again.
#
# Note that Terrafirma will NOT delete static IPs. You must manually delete
# them.
terrafirma inventory > inventory.json
terrafirma destroy
rm tf_plan.json
```


@@ 153,8 148,8 @@ If you wanted to wipe out your Terrafirma-managed infrastructure (except for
any static IPs):

```bash
TOKEN=... terrafirma -b '{}' plan > tf_plan.json
TOKEN=... terrafirma destroy
GCP_TOKEN=... terrafirma -b '{}' plan > tf_plan.json
GCP_TOKEN=... terrafirma destroy
```

## Future work