Feature/stackql deploy updates - #54
Merged
Merged
Conversation
Filter out GitHub bot accounts (type = 'Bot', e.g. claude[bot]) and the claude agent user account from the contributors list embedded in the binary via contributors.csv. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
… 2.1.0 - New protected: true field on globals and resource props, masks the rendered value in all log output (dry-run, --show-queries, DEBUG) - All log lines are scrubbed of registered secret values at the logger sink via new core/secrets module (fixed-width mask, JSON-escaped forms, longest-first replacement) - Resource-level protected export values are now also masked when they surface downstream (e.g. interpolated into a later resource query) - Stack exports display table masks protected values (files keep real values) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 36533435 | Triggered | Generic Password | ccccb99 | src/core/config.rs | View secret |
| 36533434 | Triggered | Generic Password | ccccb99 | src/core/config.rs | View secret |
| 36533436 | Triggered | Generic High Entropy Secret | ccccb99 | src/core/secrets.rs | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
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
1 participant
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.
No description provided.