From 2ec16fcf2dc81b260cb1a09284e7507d4898c313 Mon Sep 17 00:00:00 2001
From: Adam Lewis <23342526+Adam-D-Lewis@users.noreply.github.com>
Date: Wed, 1 May 2024 22:40:44 -0500
Subject: [PATCH] change ARGO_TOKEN to HERA_TOKEN

---
 docs/docs/tutorials/argo-workflows-walkthrough.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/docs/tutorials/argo-workflows-walkthrough.md b/docs/docs/tutorials/argo-workflows-walkthrough.md
index 7ffec214..a1a26117 100644
--- a/docs/docs/tutorials/argo-workflows-walkthrough.md
+++ b/docs/docs/tutorials/argo-workflows-walkthrough.md
@@ -34,7 +34,7 @@ import os
 
 global_config_host = f"https://{os.environ['ARGO_SERVER'].rsplit(':')[0]}{os.environ['ARGO_BASE_HREF']}/"
 global_config.host = global_config_host
-global_config.token = os.environ['ARGO_TOKEN']
+global_config.token = os.environ['HERA_TOKEN']
 ```
 
 ### Workflow Labels
@@ -96,7 +96,7 @@ Because this can cause substantial unexpected cloud costs, we _highly_
 recommend _always_ setting the "Time to live strategy", or `TTLStrategy` on
 every workflow.
 
-:::note 
+:::note
 The Argo UI will only show the workflow details until the
 `TTLStrategy` time has elapsed so make sure you have enough time to evaluate
 logs, etc. before those details are removed.