feat: added sql for release and release channels #4898
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
kartik-579
requested review from
prakarsh-dt,
vikramdevtron,
kripanshdevtron and
nishant-d
as code owners
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 10220829 | Triggered | Generic High Entropy Secret | 90fa8c6 | charts/devtron/devtron-bom.yaml | View secret |
| 10220829 | Triggered | Generic High Entropy Secret | 90fa8c6 | 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.
…into feature-release-v1
|
kartik-579
changed the title
github-actions
bot
added
PR:Ready-to-Review
and removed
PR:Issue-verification-failed
labels
nishant-d
approved these changes
May 13, 2024
Kishan789dev
pushed a commit
that referenced
this pull request
May 13, 2024
* added sql for relese feat * updated sql script no * renamed sql files * updated schema for release & release track * fixes in schema * updated schema * made changes in old schemas * enum correction * minor change in script * sql script update * updated script * updated sql script no * exposed release resource * updated sql script no * updated release catalog data * added rescind status change policy handling * renaming policy json field * updated schema ordering * updated global policy version * updated policy json * prod bug fix * updated policy lock status * added action check policy release * wip * updated policy for release status * updated down sql * updated sql script no. * fixed autocorrect issues * added first released on key for release * updated task run migration * Added task run down migration * sql script change * updated policy for action check - instruction patch * fixed schema merge conflict --------- Co-authored-by: Shivam-nagar23 <shivam@devtron.ai>
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 #5073
Checklist:
Does this PR introduce a user-facing change?