-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DERCBOT-1327] Git hooks - Gitleaks #1820
[DERCBOT-1327] Git hooks - Gitleaks #1820
Conversation
83a9844
to
aaadd6c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this PR 👍️
Missing :
- Config settings and ragquery exemples here : https://github.com/theopenconversationkit/tock/tree/master/gen-ai/orchestrator-server/src/main/python/tock-llm-indexing-tools/examples
Can you also add to the main README.md how to setup this hook / pre-commit, so that new developers will have the documentation.
gen-ai/orchestrator-server/src/main/python/server/.pre-commit-config.yaml
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I forgot one point, can you add to the main README.md that this project uses pre-commit ?
I agree that this README.md should have more content, we can start with this :)
Otherwise developers will forgot to enable the pre-commit hook.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks 👍️
Git hook to detect secrets such as passwords, API keys and tokens in git repositories.
Breaking change
For deployment using RAW secrets stored in mongo database or calling the Gen AI Orchestrator using raw secret (which is not advised for obvious security reasons), the format of the secret is changed key containing the secret value was previously named api_key.value is now named api_key.secret.
NB : We have not updated the existing data, as we consider that only developers use Raw-type secrets (which are subject to code refactoring)