Skip to content
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

CronJob chart new version - adds support for external secret using ClusterSecretStore #6425

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

yuvii
Copy link

@yuvii yuvii commented Feb 27, 2025

Description

Creates new cronjob chart (1.6) which fixes the CronJob chart to support ClusterSecretStore in external secret template (aligns it with devtron app template configuration).

Edit:
Also fixed #6437 - changed restartPolicy to be a variable and not hard coded (similar to how the app is set up) ,

Copy link

gitguardian bot commented Feb 27, 2025

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
2763127 Triggered Generic High Entropy Secret 0a00d51 scripts/devtron-reference-helm-charts/cronjob-chart_1-6-0/secrets-test-values.yaml View secret
141558 Triggered Generic High Entropy Secret 0a00d51 scripts/devtron-reference-helm-charts/cronjob-chart_1-6-0/env-values.yaml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. 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


🦉 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.

@satyampsoni
Copy link
Contributor

Hi @yuvii, thanks for the PR!Appreciate your contribution. We're currently considering deprecating this, so I'm putting the PR on hold for now.

@yuvii
Copy link
Author

yuvii commented Mar 27, 2025

@satyampsoni what do you mean by deprecating "this"? Are you deprecating the entire CronJob chart and it won't be an option? Or are you merging it into the basic Deployment chart in some way?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug: hard coded restartPolicy in CronJob
2 participants