Skip to content

CI passes the SWATGENX_API_KEY secret, so the two groundwater tests run again - #2

Merged
SWATGenX merged 2 commits into
mainfrom
ci/pass-api-key-secret
Sep 28, 2026
Merged

SWATGenX merged 2 commits into
mainfrom
ci/pass-api-key-secret

Conversation

@rafiei-vahid

Copy link
Copy Markdown
Collaborator

Follow-up to #1. The workflow now passes the SWATGENX_API_KEY repository secret, which holds a dedicated test account's API key. With it, test_groundwater_at_michigan and test_groundwater_at_pennsylvania call the signed-in well-record endpoint for real instead of skipping.

The keyless-message test clears the variable itself, so it still covers the keyless path when the secret is set.

🤖 Generated with Claude Code

https://claude.ai/code/session_0165nvw7C6jpq45EnoiEHE7S

rafiei-vahid and others added 2 commits September 28, 2026 20:56
…un again

The secret holds a dedicated test account's API key. Without it the two tests skip (PR #1); with it they call the
signed-in well-record endpoint for real.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0165nvw7C6jpq45EnoiEHE7S
Client falls back to the environment variable, so with the CI secret present Client(api_key="") no longer raised
(run 36468776367: DID NOT RAISE). Clearing it keeps the test on the no-key path, as the keyless groundwater test does.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0165nvw7C6jpq45EnoiEHE7S
@SWATGenX
SWATGenX merged commit c824174 into main Sep 28, 2026
2 checks passed
@SWATGenX
SWATGenX deleted the ci/pass-api-key-secret branch September 28, 2026 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants