sync: Release candidate v0.39.0 #6712
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
feat: flux cd deployment
* feat: k8s resource recommendation service integration * chore: dependency updated to 'origin/feat/k8s-resource-recommendation' * chore: updated wire_gen file * chore: dependency updated to 'origin/feat/k8s-resource-recommendation' * added vendor files
sync: Main sync develop
sync: vendor update in develop
fix: job rbac ci trigger
…fix1 fix: timeline cron change
sync: main sync 7/7
vikramdevtron
requested review from
prakarsh-dt,
nishant-d,
vivek-devtron and
pawan-mehta-dt
as code owners
|
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| {{- if $.Values.topologySpreadConstraint }} | ||
| topologySpreadConstraints: | ||
| {{ toYaml .Values.topologySpreadConstraint }} | ||
| {{- end }} |
Check warning
Code scanning / SonarCloud
Service account permissions should be restricted Medium
| {{- end}} | ||
| {{- end}} | ||
| containers: | ||
| - name: {{ $.Chart.Name }} |
Check warning
Code scanning / SonarCloud
Memory limits should be enforced Medium
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 9257608 | Triggered | Base64 AWS keys | 6fcdfe3 | scripts/devtron-reference-helm-charts/deployment-chart_4-22-0/test-values.json | View secret |
| 2763127 | Triggered | Generic High Entropy Secret | d5ef9b2 | scripts/devtron-reference-helm-charts/cronjob-chart_1-6-0/secrets-test-values.yaml | View secret |
| 141558 | Triggered | Generic High Entropy Secret | 0425751 | scripts/devtron-reference-helm-charts/deployment-chart_4-22-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?