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

build: merge upgrade to R24.05 #118

Merged
merged 46 commits into from
Aug 14, 2024
Merged

build: merge upgrade to R24.05 #118

merged 46 commits into from
Aug 14, 2024

Conversation

evegufy
Copy link
Contributor

@evegufy evegufy commented Aug 14, 2024

Description

  • merge upgrade to R24.05 into main
  • consolidate cx-central (centralidp Keycloak) to release 24.05
  • portal: set useDimWallet to true
  • docs(R24.05): improve readme (highlight note for wallet situation with R24.05)
  • improve portal adopter values file
  • change chart release and docu to download tx-data-provider from filesystem

eclipse-tractusx/sig-release#710

Pre-review checks

  • Copyright and license header are present on all affected files
  • I have performed a self-review of my changes
  • I have successfully tested the changes

ds-jhartmann and others added 30 commits June 21, 2024 11:35
Copy link

gitguardian bot commented Aug 14, 2024

⚠️ 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.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
13381440 Triggered Generic High Entropy Secret 2452260 charts/umbrella/values.yaml View secret
13381440 Triggered Generic High Entropy Secret 2452260 charts/umbrella/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.

@evegufy evegufy marked this pull request as ready for review August 14, 2024 10:41
@evegufy evegufy merged commit 73d77e5 into main Aug 14, 2024
4 checks passed
@evegufy evegufy deleted the merge/upgrade/24.05 branch August 14, 2024 11:18
@evegufy evegufy self-assigned this Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: USER READY
Development

Successfully merging this pull request may close these issues.

5 participants