Open
Conversation
…tory, service, and handler layers
…ge and update references across modules
…r deployment metrics handling
…r deployment metrics handling
…ling, enhance query ordering logic in repository
…angeRequest validation and calculation
…gic, update bulk metrics processing
…becon-2025 # Conflicts: # common-lib/utils/TimeUtils.go
misc: Added new branch in PR validator action
Co-authored-by: Shivam Nagar <124123645+Shivam-nagar23@users.noreply.github.com>
…st90Days" time windows in TimeRangeRequest validation and calculation
misc: extend(TimeUtils): add support for "last7Days", "last30Days", and "la…
* fix: update validation tags for TimeBoundariesRequest fields * fix: reset checkout message on successful fetch * Feat/finops config (#337) * feat: add cost module installation topics and configurations * feat: add cost module installation topics and time range utilities --------- Co-authored-by: Ash-exp <asutosh2000ad@gmail.com>
misc: main branch sync into kubecon-2025
…raMetrics` with `dto.Metrics`, and enhance metrics processing functions
…truction for improved readability and maintainability
misc: update DORA metrics calculation logic for single application
sync: Main sync kubecon
prakash100198
requested review from
pawan-mehta-dt,
prakarsh-dt,
vikramdevtron and
vivek-devtron
as code owners
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 21839683 | Triggered | Generic High Entropy Secret | bb059d0 | common-lib/securestore/rollback/rollback_service_test.go | View secret |
| 147804 | Triggered | Generic High Entropy Secret | bb059d0 | common-lib/securestore/rollback/vendor/github.com/caarlos0/env/.travis.yml | 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.
chore: gpu installation topic
…module dependencies for common-lib
misc: Main merge oss 2025 1
chore: OSS main branch sync
* fix: update validation tags for TimeBoundariesRequest fields * Feat/finops config (#337) * feat: add cost module installation topics and configurations * feat: add cost module installation topics and time range utilities * adding new topic for gpu installation * feat: velero backup storage location informer register * feat: storage module nats jetstream and bean * feat: bsl informer registration * feat: storage event msg struct * misc: vendor file update for velro * feat: common msg struct implementation for bsl informer * feat: vsl informer registration * feat: backup status nats message struct * feat: change in data types of backup status nats message struct * feat: backup status version datatype change * feat: backup informer registration * feat: nats message struct for restore events * feat: restore informer registration * feat: BackupSchedule status update event msg struct * feat: backup schedule resource constant * feat: backup schedule informer registration * wip: topic for velero installation * feat: refactor backup storage location status handling and clean up unused code * feat: refactor Velero event handling to use unified resource event structure * feat: enhance BackupStatus structure with additional fields for improved backup tracking * feat: streamline Velero resource event handling with new builder methods * feat: update common-lib dependency * feat: remove unused data handling methods from VeleroResourceEvent * feat: remove unused data fields and methods from VeleroResourceEvent * feat: enhance restore object change detection with backup name comparison * feat: update TLS configuration and socket handling for improved performance and deprecation cleanup * feat: update CreateOrUpdateSecretByName method to support additional data formats * feat: enhance CreateOrUpdateSecretByName method to support additional data formats * feat: add post-installation topics and groups for Velero storage * feat: add VeleroBackupSchedule client type to client.go * feat: rename ClusterVeleroBslType to ClusterStorageModuleType for clarity * feat: fix variable name typo for veleroVslInformer in informer and advisor * feat: update default value for ClusterStorageModuleType to ALL_CLUSTER * feat: enhance status comparison logic to handle nil progress and hook status * feat: improve status comparison logic to handle nil progress cases * feat: update velero informer logic to use centralized velero config * feat: add post-installation topics and update common-lib dependency * feat: add velero v1.14.1 dependency for cluster backup functionality * feat: update common-lib dependency to v0.0.0-20251205120949 for improved functionality --------- Co-authored-by: Shivam-nagar23 <shivam@devtron.ai> Co-authored-by: Shivam Nagar <124123645+Shivam-nagar23@users.noreply.github.com> Co-authored-by: ayushmaheshwari <ayush@devtron.ai> Co-authored-by: SATYAsasini <satya.prakash@devtron.ai>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
No description provided.