Merge pull request #240 from smothiki/storage

feat(storage): modify docs for configuring storage using env vars

Author: Sivaram Mothiki

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

@@ -18,12 +18,34 @@ The helm classic chart for Deis Workflow can be easily configured to connect Wor
     * Note: If you provide credentials with sufficient access to the underlying storage, Workflow components will create the buckets if they do not exist.
 * **Step 2:** If applicable, generate credentials that have write access to the storage buckets created in Step 1
 * **Step 3:** If you haven't already fetched the helm classic chart, do so with `helmc fetch deis/workflow-beta4`
-* **Step 4:** Open the helm classic chart with `helmc edit workflow-beta4` and look for the template file `tpl/generate_params.toml`
-* **Step 5:** Update the `storage` parameter to reference the storage platform you are using: `s3`, `azure`, `gcs`
-* **Step 6:** Update the values in the section which corresponds to your storage type, including region, bucket names and access credentials
+* **Step 4:** Update storage details either by setting the appropriate environment variables or by modifying the template file `tpl/generate_params.toml`
+    * **1.** Using environment variables:
+        * Set `STORAGE_TYPE` to `s3`, `azure` or `gcs`, then set the following environment variables accordingly.
+          * For `STORAGE_TYPE=gcs`:
+
+            ```
+            export GCS_KEY_JSON, GCS_REGISTRY_BUCKET, GCS_DATABASE_BUCKET, GCS_BUILDER_BUCKET
+            ```
+
+          * For `STORAGE_TYPE=s3`:
+
+            ```
+            export AWS_ACCESS_KEY, AWS_SECRET_KEY, AWS_REGISTRY_BUCKET, AWS_DATABASE_BUCKET, AWS_BUILDER_BUCKET, S3_REGION
+            ```
+
+          * For `STORAGE_TYPE=azure`:
+
+            ```
+            export AZURE_ACCOUNT_NAME, AZURE_ACCOUNT_KEY, AZURE_REGISTRY_CONTAINER, AZURE_DATABASE_CONTAINER, AZURE_BUILDER_CONTAINER
+            ```
+
+    * **2.** Using template file `tpl/generate_params.toml`:
+        * Open the helm classic chart with `helmc edit workflow-beta4` and look for the template file `tpl/generate_params.toml`
+        * Update the `storage` parameter to reference the storage platform you are using: `s3`, `azure`, `gcs`
+        * Update the values in the section which corresponds to your storage type, including region, bucket names and access credentials
     * Note: you do not need to base64 encode any of these values as Helm Classic will handle encoding automatically
-* **Step 7:** Save your changes and re-generate the helm classic chart by running `helmc generate -x manifests workflow-beta4`
-* **Step 8:** Check the generated file in your manifests directory, you should see `deis-objectstorage-secret.yaml`
+* **Step 5:** Save your changes and re-generate the helm classic chart by running `helmc generate -x manifests workflow-beta4`
+* **Step 6:** Check the generated file in your manifests directory, you should see `deis-objectstorage-secret.yaml`
 
 You are now ready to `helmc install workflow-beta4` using your desired object storage.