search

eclipse-tractusx / tutorial-resources

Apache License 2.0
11 stars 23 forks source link

feat: Shell script to deploy MXD and run performance test via Jmeter #296

Closed ciprian-nicuta closed 3 weeks ago

ciprian-nicuta commented 5 months ago

Description

  1. Created a shell script to deploy MXD in a Kubernetes Cluster using files from JMeter script.
  2. Enable Shell script to deploy Performance Test JMeter Application into another Kubernetes Cluster.
  3. Added detailed README describing the steps to perform the above tasks.
  4. Provide a sample configuration file needed to execute the performance test.
  5. Added graphics for better documentation.
  6. Added Prometheus for cluster monitoring.

Closes #286

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

gitguardian[bot] commented 5 months ago

⚠️ GitGuardian has uncovered 1 secret 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 secret in your pull request
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [-](https://dashboard.gitguardian.com/workspace/226265/incidents/secrets) | - | Generic Private Key | d37cb6c0727bdf15bbb1833f2cd99e202030b073 | mxd/performance-tests/prometheus/prometheus-ingress.yaml | [View secret](https://github.com/eclipse-tractusx/tutorial-resources/commit/d37cb6c0727bdf15bbb1833f2cd99e202030b073#diff-848a2f8b4fc2c30ff120ae8571f11c619289cc09e7f204b0c17c71b3152cdfeaL56) |
🛠 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 secret safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/specifics/base64_private_key_generic#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) 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.

ciprian-nicuta commented 5 months ago

Merge after https://github.com/eclipse-tractusx/tutorial-resources/pull/292