Add credential redaction to dokucheck CLI tool - #440
Closed
mnindrazaka wants to merge 1 commit into
Closed
Conversation
make doku-check was a go run target, so it only worked on a machine with the Go toolchain and the generated api-contract module. Neither is present on the VPS, which left no way to test the live DOKU credentials there. build-release now also compiles cmd/dokucheck into dist/release, so the existing deploy tarball carries it to the box. Identifiers are redacted in its output so it is safe to run where the log is public; -show-credentials prints them in full. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01S4JVnnR1QZd4HpDPe3Em78
|
Deployment failed for project gatherloop-pos with the following error: Learn More: https://vercel.com/m-nindra-zakas-projects-ae6b8849?upgradeToPro=build-rate-limit |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a command-line flag to the
dokucheckutility to control whether sensitive credentials are displayed in full or redacted in the output. By default, credentials are now redacted to make the tool's output safe for CI logs and public sharing.Changes:
-show-credentialsflag todokucheckcommand with default behavior of redacting sensitive valuesformat()helper function that redacts credentials by default, showing either a character count for short values or first/last 4 characters with total length for longer valuesdoku-checkmake target to pass-show-credentialsflag for local development usedokucheckto the release build process so it can be deployed as a standalone binary on the VPSThe redaction strategy preserves enough information to verify credential format while preventing accidental exposure in logs.
https://claude.ai/code/session_01S4JVnnR1QZd4HpDPe3Em78