Skip to content
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

docs: Created a file for listing Devtron Users #5310

Merged
merged 15 commits into from
Jun 14, 2024

Conversation

siddhant-khisty
Copy link
Contributor

@siddhant-khisty siddhant-khisty commented Jun 14, 2024

Description

Fixes #5311

Checklist:

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR requires documentation updates?
  • I've updated documentation as required by this PR.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have tested it for all user roles.
  • I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?


Copy link

gitguardian bot commented Jun 14, 2024

⚠️ GitGuardian has uncovered 2 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.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
10220829 Triggered Generic High Entropy Secret 876b8f3 charts/devtron/devtron-bom.yaml View secret
10220829 Triggered Generic High Entropy Secret 876b8f3 charts/devtron/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


🦉 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.

@abhibhaw abhibhaw changed the title DOCS: Created a file for listing Devtron Users docs: Created a file for listing Devtron Users Jun 14, 2024
nishant-d
nishant-d previously approved these changes Jun 14, 2024
Copy link

sonarcloud bot commented Jun 14, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
1.7% Duplication on New Code

See analysis details on SonarCloud

@abhibhaw abhibhaw merged commit df0f0e5 into devtron-labs:main Jun 14, 2024
4 checks passed
@siddhant-khisty siddhant-khisty deleted the user-update branch June 17, 2024 04:36
@siddhant-khisty siddhant-khisty restored the user-update branch June 17, 2024 04:40
@siddhant-khisty siddhant-khisty deleted the user-update branch June 17, 2024 04:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Doc: Create a seperate file for people and organizations using Devtron
3 participants