fix: Bulk deploy panic and docker tag handling #5949
Merged
Conversation
This file contains 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
* wip: adding app name check * wip * wip * wip * moving migration to code * wip: adding app name in log * wip: moving sql logic to code * pg no rows handling * adding db migration call * fixing fetch app query * wip: adding pg multiple rows handling * audit log update
fix: nil ptr fix in copying extraEnvVars
* added up script for docker linit plugin * rename of script file * docker lint down script * changes in docker lint * hadolint image * change in name of plugin * changes in down script * chnages in docker lint * chnages in down script * change in hadolint image * rename down script file * renaming sql script
* Create 028901_019_devtron_ci_trigger_v1_1.down.sql * Create 028901_019_devtron_ci_trigger_v1_1.up.sql * Update 028901_019_devtron_ci_trigger_v1_1.up.sql --------- Co-authored-by: Prakarsh <71125043+prakarsh-dt@users.noreply.github.com>
* Update Chart.yaml * Update devtron-bom.yaml * Update values.yaml * Update devtron-installer.yaml * Update installation-script * Update version.txt * Update devtron.yaml * Update releasenotes.md * Update devtron-bom.yaml * Update values.yaml * Update releasenotes.md * Update releasenotes.md * Updated release-notes files * Update releasenotes.md * Update release.txt * Updated release-notes files * Update release-notes-v0.7.2.md --------- Co-authored-by: ReleaseBot <prakarsh@devtron.ai>
…panic-fixes misc: err handling for configmap access
iamayushm
requested review from
prakarsh-dt,
vikramdevtron,
nishant-d and
pawan-mehta-dt
as code owners
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 10220829 | Triggered | Generic High Entropy Secret | 38dc073 | charts/devtron/devtron-bom.yaml | View secret |
| 10220829 | Triggered | Generic High Entropy Secret | 38dc073 | charts/devtron/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.
iamayushm
changed the title
|
nishant-d
approved these changes
Oct 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #963
Checklist:
Does this PR introduce a user-facing change?