Conversation
Comprehensive documentation audit revealed several discrepancies between code and documentation. This commit addresses all identified issues: Documentation Fixes: - Update dependency count from 230+ to 330+ in dependencies.md (3 locations) - Add missing 'docker' category to doctor --category flag documentation - Document missing --force/-f flag in dockerize command - Update version example in installation.md to use generic vX.Y.Z placeholder Sidebar Improvements: - Add missing 'haft docker' command to sidebar - Add missing 'haft doctor' command to sidebar - Add missing 'haft generate scheduler' subcommand for consistency Code Improvements: - Align catalog.go category names with documentation: * 'Data' -> 'Data Processing' * 'AI' -> 'AI & Machine Learning' * 'Maps' -> 'Maps & Geo' - Improves CLI output consistency when running 'haft add --list' Files changed: - docs/docs/commands/docker.md - docs/docs/commands/doctor.md - docs/docs/guides/dependencies.md - docs/docs/installation.md - docs/sidebars.ts - internal/cli/add/catalog.go All changes verified against source code in internal/cli/ to ensure 100% alignment between implementation and documentation.
…rompts - Add smart merge functionality for docker-compose.yml that preserves user customizations - Always prompt for database selection in interactive mode (not just when JPA detected) - Add --force/-f flag to completely overwrite existing files when needed - Merge logic preserves custom env vars, volumes, build configs, and container names - Add database services without removing existing configurations - Add comprehensive tests for merge functionality and force overwrite - Improve UX with clear feedback messages (Merged, Added, Updated, Overwritten) This makes the dockerize workflow iterative and non-destructive, allowing users to evolve their Docker setup without losing customizations.
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 24571530 | Triggered | Generic Password | 72abb5d | internal/cli/docker/docker_test.go | 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 secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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.