updated env params

swigerb · Aug 15, 2024 · 24d28cc · 24d28cc
1 parent d5cf5e7
commit 24d28cc
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 13 deletions.
diff --git a/.github/workflows/azure-dev.yml b/.github/workflows/azure-dev.yml
@@ -15,32 +15,23 @@ permissions:
   id-token: write
   contents: read
 
-env:
-  # edit these to match the names of your environments
-  # dev_env: <dev_env_name>
-  # test_env: <test_env_name>
-  # prod_env: <prod_env_name>
-  dev_env: ghdev
-  test_env: ghtest
-  prod_env: ghprod
-
 jobs:
   deploy-dev:
     uses: ./.github/workflows/deploy-template.yml
     secrets: inherit
     with:
-      AZURE_ENV_NAME: $dev_env
+      AZURE_ENV_NAME: ghdev # edit to match the name of your environment
 
   deploy-test:
     uses: ./.github/workflows/deploy-template.yml
     secrets: inherit
     needs: [deploy-dev]
     with:
-      AZURE_ENV_NAME: $test_env
+      AZURE_ENV_NAME: ghtest # edit to match the name of your environment
 
   deploy-prod:
     uses: ./.github/workflows/deploy-template.yml
     secrets: inherit
     needs: [deploy-test]
     with:
-      AZURE_ENV_NAME: $prod_env
+      AZURE_ENV_NAME: ghprod # edit to match the name of your environmen
diff --git a/docs/GH-SETUP.md b/docs/GH-SETUP.md
@@ -210,7 +210,7 @@ rm federated_id.json # clean up temp file
 ## 4. Modify the workflow files as needed for deployment
 
 > [!IMPORTANT]
-> - The environment names in the below described `azure-dev.yml` **need to be edited to match the environment names you created**. In the file, these variables are set in the `env` block, with a comment stating `edit these to match the names of your environments`.
+> - The environment names in the below described `azure-dev.yml` **need to be edited to match the environment names you created**. In the file, these values are passed into the template as the `AZURE_ENV_NAME`, with a comment stating `edit to match the name of your environment`. _If you don't edit these values, the workflow will not work properly_.
 > - The `workflow_dispatch` in the `azure-dev.yml` file is set to trigger on push to a branch `none`. You may modify this to trigger on a specific branch or event.
 
 - The following files in the `.github/workflows` folder are used to deploy the infrastructure and services to Azure: