Introducing Devtron Guru on Gurubase.io

[kursataktas]

Hello team,

I'm the maintainer of Anteon. We have created Gurubase.io with the mission of building a centralized, open-source tool-focused knowledge base. Essentially, each "guru" is equipped with custom knowledge to answer user questions based on collected data related to that tool.

I wanted to update you that I've manually added the Devtron Guru to Gurubase. Devtron Guru uses the data from this repo and data from the docs to answer questions by leveraging the LLM.

In this PR, I showcased the "Devtron Guru", which highlights that Devtron now has an AI assistant available to help users with their questions. Please let me know your thoughts on this contribution.

Additionally, if you want me to disable Devtron Guru in Gurubase, just let me know that's totally fine.

[kursataktas]

Hey everyone, have you had a chance to check this out?

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9257608	Triggered	Base64 AWS keys	f56bb62	scripts/devtron-reference-helm-charts/deployment-chart_4-20-0/test-values.json	View secret
2763127	Triggered	Generic High Entropy Secret	f56bb62	scripts/devtron-reference-helm-charts/deployment-chart_4-20-0/secrets-test-values.yaml	View secret
141558	Triggered	Generic High Entropy Secret	f56bb62	scripts/devtron-reference-helm-charts/deployment-chart_4-20-0/env-values.yaml	View secret
141558	Triggered	Generic High Entropy Secret	f56bb62	scripts/devtron-reference-helm-charts/reference-chart_4-19-0/env-values.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. 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.}

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud