Skip to content

fix(export): expand --redact-secrets for sanitize delivery - #70

Merged
fmenesesg merged 1 commit into
mainfrom
feat/export-sensitive-redaction-gap
Oct 14, 2026
Merged

fmenesesg merged 1 commit into
mainfrom
feat/export-sensitive-redaction-gap

Conversation

@fmenesesg

Copy link
Copy Markdown
Collaborator

Summary

  • Expand --redact-secrets to the full consulting sanitize key set from the BPBA security finding (certificates/PEM, password, apikey, secret_token, username, infra URLs, issuer endpoints).
  • Strip multi-line YAML PEM bodies under certificate / certificate_key.
  • Run redaction after manifest.json write so admin_url is covered.
  • Issuer URLs are fully redacted (no longer host-preserved).

Test plan

  • go test ./internal/export/ -count=1
  • go test ./... -count=1
  • Re-export with --redact-secrets and confirm listed keys are ***REDACTED*** (no PEM leftovers)

Closes consulting concern for cleartext secrets in sizing exports (related discussion / client mail).

Made with Cursor

Cover the consulting key set (certs/PEM blocks, passwords, apikey,
secret_token, username, and infra URLs) so client exports used for
sizing do not retain cleartext secrets. Fully redact issuer endpoints
and run redaction after writing manifest.json.

Co-authored-by: Cursor <[email protected]>
@fmenesesg fmenesesg added the type:bugfix Non-breaking bug fix label Oct 14, 2026
@fmenesesg
fmenesesg requested a review from pcastelo as a code owner October 14, 2026 14:13
@fmenesesg
fmenesesg merged commit e712277 into main Oct 14, 2026
1 check passed
@fmenesesg
fmenesesg deleted the feat/export-sensitive-redaction-gap branch October 14, 2026 14:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type:bugfix Non-breaking bug fix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant