${{ steps.fruit.output.action_fruit }}

${{ steps.fruit.outputs.action_fruit }}

name: 'test-global-env-var'

on:
  push:
    branches: [ "dev-*" ]

permissions:
  actions: read
  contents: read
  security-events: write

env:
  AWS_DEFAULT_REGION: us-west-2

defaults:
  run:
    shell: bash

jobs:
  # This appears to be the only way to re-use global env vars in reusable workflows, as of 1/2023
  set-global-env-var:
    runs-on: ubuntu-latest
    outputs:
      aws_region_via_cli: ${{ steps.set-vars.outputs.aws_region }}
    steps:
      - name: set-vars-via-cli
        env:
          AWS_REGION: ${{ env.AWS_DEFAULT_REGION }}
        id: set-vars
        run: |
          echo "aws_region=${AWS_REGION}" >> $GITHUB_OUTPUT
          echo "concurrency_string=${{ format('{0}-env', github.workflow) }}" >> $GITHUB_OUTPUT

  reuse-global-var-in-actions:
    runs-on: ubuntu-latest
    needs:
      - set-global-env-var
    steps:
      - name: use-global-directly
        uses: actions/hello-world-javascript-action@master
        with:
            who-to-greet: ${{ env.AWS_DEFAULT_REGION }}

      # here env needs to be specified again for each step in each job where it is used
      # -- and then it needs to be repeated in the input for the job
      # This is too much work-around for the slight effect it gives.
      - name: use-var-by-job
        uses: actions/hello-world-javascript-action@master
        env:
          AWS_REGION: ${{ env.AWS_DEFAULT_REGION }}
        with:
            who-to-greet: ${{ env.AWS_REGION }}

      - name: reuse-global-var-consistently
        uses: actions/hello-world-javascript-action@master
        with:
            who-to-greet: ${{ needs.set-global-env-var.outputs.aws_region_via_cli }}

  reuse-global-var-in-workflow:
    needs:
      - set-global-env-var
    concurrency:
      group: ${{ needs.reuse-global-var.outputs.concurrency_string }}
      # included to demonstrate that needs works here
    uses: Company/repo/.github/workflows/test-reusable-workflow.yml@master
    with:
      env_name: ${{ env.AWS_DEFAULT_REGION }}

    # This should succeed. But it fails even before run-time like this:
    #  Invalid workflow file: .github/workflows/test-glob-env.yml#L76
    #  The workflow is not valid. .github/workflows/test-glob-env.yml (Line: 76, Col: 17): 
    #  Unrecognized named-value: 'env'. Located at position 1 within expression: env.AWS_DEFAULT_REGION
    #
    # It's silly to have to have to code additional complexity because the global env context 
    #    is not available to reusable workflows.
    # Additionally, it's misleading and confusing when it is available to actions, as above.
    # It cost me 45 minutes to hunt this down, and untold hours trying to figure out why the code
    #    didn't work before I had enough context to hunt it down.
    #    It may also be noteworthy that I originally ultimately concluded incorrectly 
    #    that the global env context was unavailable to any job inputs.

on:
  workflow_call:
    inputs:
      env_name:
        required: true
        type: string

defaults:
  run:
    shell: bash

jobs:
  test-global-for-input:
    name: Test global for input
    runs-on: ubuntu-latest
    steps:
        - run: |
            echo "Passed input: ${{ inputs.env_name }}