fix: forward NOMAD_TOKEN to $GITHUB_ENV for shell access

Job-level env vars from secrets aren't injected as real shell env
vars in Docker-based composite actions. Bridge via $GITHUB_ENV,
same pattern as NOMAD_ADDR.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Christopher Mühl 2026-02-18 01:22:08 +01:00
parent ee3dfcb19a
commit 72569d2a53
No known key found for this signature in database
GPG key ID: 925AC7D69955293F

View file

@ -29,8 +29,9 @@ runs:
# Install AWS CLI # Install AWS CLI
nix profile install nixpkgs#awscli2 nix profile install nixpkgs#awscli2
# Set Nomad address # Set Nomad connection
echo "NOMAD_ADDR=http://alvin:4646" >> $GITHUB_ENV echo "NOMAD_ADDR=http://alvin:4646" >> $GITHUB_ENV
echo "NOMAD_TOKEN=${{ env.NOMAD_TOKEN }}" >> $GITHUB_ENV
- name: Build site with Nix - name: Build site with Nix
shell: bash shell: bash