sync: Main sync develop #6583
Merged
sync: Main sync develop #6583
Conversation
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
docs: updated development.md
chore: rollout reference chart 5-1-0
misc: Sync reference charts to main
fix: Remove funtionName from labels from pg_query_duration_seconds_* metrics
* Updated release-notes files * Update beta-releasenotes.md * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * misc: exposed the postgres endpoint in migrator and app-sync (#6570) * exposed the postgres endpoint * renamed the parameter --------- Co-authored-by: Badal Kumar Prusty <[email protected]> * Switched Kubelink to Headless mode & added retention for minio-cache-bucket * Updated minio added statement for no retention policy * Updated release notes * updated minio condition * Updated notifier to 99e2f3cd-372-32893 tag in values file * Updated kubewatch to da156379-419-32900 tag in values file * Updated kubelink to da156379-564-32903 tag in values file * Updated git-sensor to da156379-200-32905 tag in values file * Updated dashboard to c5dfd7aa-690-32907 tag in values file * Updated release notes * Updated lens to da156379-333-32910 tag in values file * Updated ci-runner to da156379-138-32911 tag in values file * Updated image-scanner to da156379-141-32912 tag in values file * Updated chart-sync to da156379-836-32914 tag in values file * Updated hyperion to fe2a86b-280-32916 tag in values file * Updated devtron to fe2a86b-434-32917 tag in values file * Updated the version in scripts * sorted the devtron-images.txt.source * Update devtron-bom.yaml * Update kubelink.yaml * Update devtron.yaml * Updated devtron to ccae002-434-32949 tag in values file * Updated hyperion to ccae002-280-32950 tag in values file * Updated devtron to 667bd63-434-32952 tag in values file * Updated hyperion to 667bd63-280-32953 tag in values file * Update releasenotes.md * Update release-notes-v1.6.0.md * Update release-notes-v1.6.0.md * Update releasenotes.md * Update release-notes-v1.6.0.md * Update releasenotes.md * Update release-notes-v1.6.0.md * Update releasenotes.md * Update releasenotes.md * Update release-notes-v1.6.0.md * Update Chart.yaml * Update devtron-bom.yaml --------- Co-authored-by: akshatsinha007 <[email protected]> Co-authored-by: Badal Kumar <[email protected]> Co-authored-by: Badal Kumar Prusty <[email protected]> Co-authored-by: akshatsinha007 <[email protected]> Co-authored-by: Pawan Mehta <[email protected]>
vikramdevtron
requested review from
nishant-d,
pawan-mehta-dt,
prakarsh-dt and
vivek-devtron
as code owners
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 9257608 | Triggered | Base64 AWS keys | 667bd63 | scripts/devtron-reference-helm-charts/deployment-chart_4-21-0/test-values.json | View secret |
| 2763127 | Triggered | Generic High Entropy Secret | fc4aa57 | scripts/devtron-reference-helm-charts/deployment-chart_4-21-0/secrets-test-values.yaml | View secret |
| 141558 | Triggered | Generic High Entropy Secret | a92dcd5 | scripts/devtron-reference-helm-charts/deployment-chart_4-21-0/env-values.yaml | 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.
|
The migration files have successfully passed the criteria!! |
|
The migration files have successfully passed the criteria!! |
|
vivek-devtron
approved these changes
May 19, 2025
pawan-mehta-dt
approved these changes
May 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
12 participants
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.
Description
Fixes #
Checklist:
Does this PR introduce a user-facing change?