chore: Merge branch 'origin/main' into 'release-candidate-v0.44.0' #6897
Conversation
…o user_deployment_request table (#6888) Co-authored-by: Ash-exp <asutosh2000ad@gmail.com>
…sion for externalSecrets (#6892) * Added new chart version 4-22-0 for deployment * added new chart version 5-2-0 for statefulset * Added sql for latest chart 4.22.0 * Added sql for latest statefulset chart 5.2.0 * Update 34704403_deployment-chart-ref_4-22-0.up.sql * Update 34704404_statefulset_5_2_0.up.sql * Update 34704404_statefulset_5_2_0.down.sql
…de tableName for PostgreSQL compatibility
* added rollout-chart-5-1-1 * added name = 'Rollout Deployment' * added reference-chart_5-1-1 * Update 34604602_reference-5-1-1.down.sql * switched the chart version from 5.1.1 to 5.2.0 * took changes of deployement-4-22 * added migration * Delete scripts/sql/34604602_reference-5-2-0.up.sql * Delete scripts/sql/34604602_reference-5-2-0.down.sql
misc: update UserDeploymentRequestWithAdditionalFields struct to include tableName for PostgreSQL compatibility
Ash-exp
requested review from
pawan-mehta-dt,
prakarsh-dt,
vikramdevtron and
vivek-devtron
as code owners
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 9257608 | Triggered | Base64 AWS keys | f733a1d | scripts/devtron-reference-helm-charts/deployment-chart_4-22-0/test-values.json | View secret |
| 2763127 | Triggered | Generic High Entropy Secret | 880110d | scripts/devtron-reference-helm-charts/reference-chart_5-2-0/secrets-test-values.yaml | View secret |
| 141558 | Triggered | Generic High Entropy Secret | f733a1d | scripts/devtron-reference-helm-charts/statefulset-chart_5-2-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.
|
Bito Automatic Review Skipped - Branch Excluded |
|
Description
Fixes #
Checklist:
Does this PR introduce a user-facing change?