Skip to content

fix: don't print credentials to stdout on login unless --no-cache#8

Merged
alukach merged 1 commit into
mainfrom
worktree-login-no-stdout
Jun 26, 2026
Merged

fix: don't print credentials to stdout on login unless --no-cache#8
alukach merged 1 commit into
mainfrom
worktree-login-no-stdout

Conversation

@alukach

@alukach alukach commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Problem

source-coop login always printed the resolved AWS credentials to stdout, regardless of --no-cache. During demos this leaks credentials onto the terminal/recording every time.

Change

Credentials now go to stdout only when --no-cache is passed:

  • source-coop login → caches silently, no creds on stdout, prints Run 'source-coop creds' to print them.
  • source-coop login --no-cache → prints creds to stdout (nothing is cached, so output is the only way to get them)
  • source-coop creds → unchanged

This matches the --no-cache flag's existing doc comment ("just print to stdout") and the separate creds command whose job is printing.

Test

No tests in this repo and the change is a branch swap; verified with cargo build and cargo fmt --check.

🤖 Generated with Claude Code

login always dumped credentials to stdout, which leaks them during
demos. Now the default path caches silently and points the user at
`source-coop creds`; stdout output only happens with --no-cache, where
nothing is cached and printing is the only way to get the creds.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@alukach alukach merged commit 792ea5e into main Jun 26, 2026
9 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