ref(upgrading-workflow): use -w 0 flag when base64 encoding

src/installing-workflow/configuring-object-storage.md

@@ -44,7 +44,7 @@ Operators should configure object storage by editing the Helm values file before
 	All values will be automatically (base64) encoded _except_ the `key_json` values under `gcs`/`gcr`.  These must be base64-encoded.  This is to support cleanly passing said encoded text via `helm --set` cli functionality rather than attempting to pass the raw JSON data.  For example:
 
 		$ helm install workflow --namespace deis \
-			--set global.storage=gcs,gcs.key_json="$(cat /path/to/gcs_creds.json | base64 | tr -d '[:space:]')"
+			--set global.storage=gcs,gcs.key_json="$(cat /path/to/gcs_creds.json | base64 -w 0)"
 
 You are now ready to run `helm install deis/workflow --namespace deis -f values.yaml` using your desired object storage.
 

src/managing-workflow/upgrading-workflow.md

@@ -35,7 +35,7 @@ $ helm upgrade deis/workflow
 **Note:** If using off-cluster object storage on [gcs](https://cloud.google.com/storage/) and/or off-cluster registry using [gcr](https://cloud.google.com/container-registry/) and intending to upgrade from a pre-`v2.10.0` chart to `v2.10.0` or greater, the `key_json` values will now need to be pre-base64-encoded.  Therefore, assuming the rest of the custom/off-cluster values are defined in the existing `values.yaml` used for previous installs, the following may be run:
 
 ```
-$ B64_KEY_JSON="$(cat ~/path/to/key.json | base64 | tr -d '[:space:]')"
+$ B64_KEY_JSON="$(cat ~/path/to/key.json | base64 -w 0)"
 $ helm upgrade <release_name> deis/workflow -f values.yaml --set gcs.key_json="${B64_KEY_JSON}",registry-token-refresher.gcr.key_json="${B64_KEY_JSON}"
 $ # alternatively, simply replace the appropriate values in values.yaml and do without the `--set` parameter
 ```