Formatting and date change

Signed-off-by: Andrew Cornies <[email protected]>

Author: acornies

_posts/2019-04-05-openfaas-on-nomad.md renamed to _posts/2019-03-18-openfaas-on-nomad.md

@@ -1,7 +1,7 @@
 ---
 title: "A Reintroduction to OpenFaaS on Nomad"
 description: Andrew Cornies reintroduces the faas-nomad provider. Learn why running OpenFaaS on Nomad is a compelling alternative to start your Serverless journey.
-date: 2019-04-05
+date: 2019-03-18
 image: /images/openfaas-on-nomad/abstract-blaze-bonfire-211157.jpg
 categories:
   - nomad
@@ -64,53 +64,58 @@ Let's look at the Vault integration more closely:
 Let's provision a Vault instance to handle the secrets API of OpenFaaS:
 
 Reference example:
-https://raw.githubusercontent.com/hashicorp/faas-nomad/master/provisioning/scripts/vault_populate.sh
+[https://raw.githubusercontent.com/hashicorp/faas-nomad/master/provisioning/scripts/vault_populate.sh](https://raw.githubusercontent.com/hashicorp/faas-nomad/master/provisioning/scripts/vault_populate.sh)
 
 1) Enable the approle auth backend in Vault:
 
-   `vault auth enable approle`
+```shell
+vault auth enable approle
+```
 
 2) Create a policy for faas-nomad and OpenFaaS functions:
 
-   `vault policy write openfaas policy.hcl`
+```shell
+vault policy write openfaas policy.hcl
+```
 
-   Policy file example: https://raw.githubusercontent.com/hashicorp/faas-nomad/master/provisioning/scripts/policy.hcl
+   Policy file example: [https://raw.githubusercontent.com/hashicorp/faas-nomad/master/provisioning/scripts/policy.hcl](https://raw.githubusercontent.com/hashicorp/faas-nomad/master/provisioning/scripts/policy.hcl)
 
    It is important that the policy contain: create, update, delete and list capabilities that match your secret backend prefix. In this case, path "secret/openfaas/*" will work with the default configuration.
 
    Also, faas-nomad takes care of renewing it's own auth token, so we need to make sure the policy uses path "auth/token/renew-self" and has the "update" capability.
 
 3) Setup the approle itself:  
-   ```
-   curl -i \
-     --header "X-Vault-Token: ${VAULT_TOKEN}" \
-     --request POST \
-     --data '{"policies": ["openfaas"], "period": "24h"}' \
-     https://${VAULT_HOST}/v1/auth/approle/role/openfaas
-   ```
+```shell
+curl -i \
+  --header "X-Vault-Token: ${VAULT_TOKEN}" \
+  --request POST \
+  --data '{"policies": ["openfaas"], "period": "24h"}' \
+  https://${VAULT_HOST}/v1/auth/approle/role/openfaas
+```
    This creates the role attached to the policy we just created. The "period" property and duration is important for renewing long-running service Vault tokens.
-   ```
-   curl -i \
-     --header "X-Vault-Token: ${VAULT_TOKEN}" \
-     https://${VAULT_HOST}/v1/auth/approle/role/openfaas/role-id
-   ```
-   Produces the role_id needed for -vault_app_role_id cli argument.
-   ```
-   curl -i \
-     --header "X-Vault-Token: ${VAULT_TOKEN}" \
-     --request POST \
-     https://VAULT_HOST}/v1/auth/approle/role/openfaas/secret-id
-   ```
+```shell
+curl -i \
+  --header "X-Vault-Token: ${VAULT_TOKEN}" \
+  https://${VAULT_HOST}/v1/auth/approle/role/openfaas/role-id
+```
+Produces the role_id needed for -vault_app_role_id cli argument.
+```shell
+curl -i \
+  --header "X-Vault-Token: ${VAULT_TOKEN}" \
+  --request POST \
+  https://${VAULT_HOST}/v1/auth/approle/role/openfaas/secret-id
+```
    Produces the secret_id needed for -vault_app_secret_id cli argument.
 
 Let's assume the Vault parameters have been populated in the run args, and you're now running faas-nomad along with the other OpenFaaS components. Now, try out the new faas-cli secret commands:
 
-```
-faas-cli secret create grafana_api_token --from-literal=foo --gateway ${FAAS_GATEWAY}
+```shell
+faas-cli secret create grafana_api_token --from-literal=foo \
+  --gateway ${FAAS_GATEWAY}
 ```
 
 Now we can use our newly created secret “grafana_api_token” in a new function we want to deploy:
-```
+```shell
 faas-cli deploy --image acornies/grafana-annotate \
   --name grafana-annotate --secret grafana_api_token \
   --env grafana_url=http://grafana.service.consul:3000