Skip to content

fix: export the nats seed file as an absolute path in integration tests #59

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
muhammad-tahir-nawaz merged 1 commit into from
Oct 14, 2026
Merged

fix: export the nats seed file as an absolute path in integration tests #59

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions .github/workflows/integration-tests.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -209,7 +209,8 @@ jobs:

# NATS client auth takes an nkey seed from a *file*, but the value arrives
# from Keeper as an env var. Write it to the path callers already point
# NATS_NKEY_SEED_FILE at, so no artifact has to carry a credential.
# NATS_NKEY_SEED_FILE at, so no artifact has to carry a credential. The path is
# absolute because the server and test script run in inputs.working_directory.
- name: Materialise NATS nkey seed file
if: ${{ inputs.use_nats || inputs.use_nats_port_forward }}
run: |
Expand All @@ -220,7 +221,7 @@ jobs:
fi
umask 077
printf '%s' "$NATS_NKEY_SEED" > ./nats-nkey.seed
echo "NATS_NKEY_SEED_FILE=./nats-nkey.seed" >> "$GITHUB_ENV"
echo "NATS_NKEY_SEED_FILE=$PWD/nats-nkey.seed" >> "$GITHUB_ENV"

- name: Set up Go
uses: actions/setup-go@v4
Expand Down
Loading