Skip to content

fix: avoid exposing sensitive info in auth verification step#3

Merged
stack72 merged 1 commit into
mainfrom
fix/mask-whoami-output
Jul 4, 2026
Merged

fix: avoid exposing sensitive info in auth verification step#3
stack72 merged 1 commit into
mainfrom
fix/mask-whoami-output

Conversation

@stack72

@stack72 stack72 commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

Summary

  • The swamp auth whoami command was printing full user details (email, collectives, etc.) into CI logs
  • Changed to use --json output with jq to check only the authenticated field
  • Prints a generic success/error message instead of the raw whoami response

Test plan

  • Verify the auth test workflow passes with a valid SWAMP_API_KEY
  • Confirm CI logs no longer contain user email, collectives, or other sensitive fields

🤖 Generated with Claude Code

The whoami command outputs user details (email, collectives, etc.) into
the CI logs. Use --json output with jq to check only the authenticated
field, and print a generic success message instead.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@stack72
stack72 merged commit c2608c1 into main Jul 4, 2026
5 checks passed
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.

1 participant