-
Notifications
You must be signed in to change notification settings - Fork 553
sync: Release candidate v0.38.0 #6680
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
Conversation
# Conflicts: # go.mod # go.sum # vendor/github.com/devtron-labs/common-lib/utils/k8s/K8sUtil.go # vendor/modules.txt
# Conflicts: # go.mod # go.sum # vendor/modules.txt
sync: Develop main sync
fix: incorrect data for git trigger history at app detail page
sync: Develop main sync
* removed hardcoded dependencies * k8s upgrade * helm and argo upgrade * helm and argo upgrade * golang.org/x/net upgrade * golang.org/x/net upgrade * DeleteProject gitlab client changes * common-lib sync * common lib sync * common-lib sync
fix: panic handling on cd trigger
# Conflicts: # env_gen.json # go.mod # go.sum # pkg/delete/DeleteService.go # vendor/modules.txt
# Conflicts: # go.mod # go.sum # vendor/modules.txt
…n-oss chore: when a cluster event occurs, create config map instead of secret
* refact * app count events * app count events * app count events * app count events * query fix * policies included * wip * query fix posthog query * removed extra dockerFile count queries * fix * fix
* fix: gitops provider multiple save error * updated const ArgoRepoSyncDelayErr as per new ArgoCd update * fix: unable resolve 'HEAD' to a commit SHA * fix: git clone issue for empty repository * fix: ambiguous argument 'origin/HEAD': unknown revision or path not in the working tree. * fix: SSH known host confirmation issue on cloning * chore: updated default value of ARGO_REPO_REGISTER_RETRY_COUNT * chore: incorporated review comments * chore: removed dead code * chore: minor refactorings * chore: added integration test cases * fix: added handling for argocd older versions
* panic fixes (#6657) * fix-cd-pipeline-check (#6658) * vendor update on develop --------- Co-authored-by: Shivam Nagar <[email protected]>
* panic fixes (#6657) * fix-cd-pipeline-check (#6658) * release: PR for v1.7.0 (#6667) * Updated release-notes files * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * removed init-container from git-sensor (#6605) Co-authored-by: Badal Kumar Prusty <[email protected]> * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * feat: added support for loadBalancerIP (#6617) * added support for loadBalancerIP * removed default value for loadBalancerIP --------- Co-authored-by: Badal Kumar Prusty <[email protected]> * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * Updated release notes * set fsGroup to allow non-root app to write to PVC (#6664) Co-authored-by: Badal Kumar Prusty <[email protected]> * misc: Shifted the dbConfigs under global (#6621) * Shifted the dbConfigs under global * updated the configurations for external database support * handled casbin migration case for database name * added support for custom annotations for ci-runner cd-runner and devtron * switched the conditioning to handle devtron-bom.yaml * removed check of values.global from postgresql.yaml * Updated kubewatch to a4fc9044-419-33852 tag in values file * Updated kubelink to a4fc9044-564-33855 tag in values file * Updated devtron to c8e75fb-434-33854 tag in values file * added support for nfs (#6665) Co-authored-by: Badal Kumar Prusty <[email protected]> * Updated lens to a4fc9044-333-33874 tag in values file * Updated git-sensor to a4fc9044-200-33872 tag in values file * Updated dashboard to a85f2624-690-33873 tag in values file * Updated ci-runner to a4fc9044-138-33875 tag in values file * Updated notifier to 19d654ff-372-33876 tag in values file * Updated image-scanner to a4fc9044-141-33877 tag in values file * Updated chart-sync to a4fc9044-836-33878 tag in values file * Updated hyperion to c8e75fb-280-33879 tag in values file * Updated the nfs condition * Updated the version in scripts * updated release-notes file * Updated releasenotes.md * Updated release-notes-v1.7.0.md * finalized releasenotes --------- Co-authored-by: Badal Kumar <[email protected]> Co-authored-by: Badal Kumar Prusty <[email protected]> Co-authored-by: akshatsinha007 <[email protected]> Co-authored-by: akshatsinha007 <[email protected]> * vendor update on rc --------- Co-authored-by: Shivam Nagar <[email protected]> Co-authored-by: systemsdt <[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: akshatsinha007 <[email protected]>
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
2763127 | Triggered | Generic High Entropy Secret | c1038ba | scripts/devtron-reference-helm-charts/gpu-workload-4-21-0/secrets-test-values.yaml | View secret |
141558 | Triggered | Generic High Entropy Secret | c1038ba | scripts/devtron-reference-helm-charts/gpu-workload-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.
|
Description
Fixes #
Checklist:
Does this PR introduce a user-facing change?