Forked Repository

[GM33]

What changes were proposed in this pull request?

How was this pull request tested?

Developer's Certificate of Origin 1.1

   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 12 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
-		IBM COS HMAC Credentials	a10138ed7536d278b2a846a7118e0a4ddfd415f1	component-library/util/util-cos.ipynb	View secret
-		IBM COS HMAC Credentials	c661da3e1007afd7c3e6af190dcb1195e8153025	component-library/util/util-cos.ipynb	View secret
-		IBM COS HMAC Credentials	ae45733090f2f46f48b82668bcd0a5ce4f2085d3	component-library/util/util-cos.ipynb	View secret
-		IBM COS HMAC Credentials	9f906e10085212cb56b6a4934b068e65684f95c6	component-library/util/util-cos.ipynb	View secret
8658480	Triggered	Generic High Entropy Secret	3734c25bd6b4c968173efd033b3f7f1b54045a57	coursera_ai/week2/keras/keras_fashion_mnist.ipynb	View secret
8658480	Triggered	Generic High Entropy Secret	d08d3c40ee50982a8cd4a6249960286b9ddb135e	coursera_ai/week2/keras/keras_fashion_mnist.ipynb	View secret
8658481	Triggered	Generic High Entropy Secret	3734c25bd6b4c968173efd033b3f7f1b54045a57	coursera_ai/AssignmentKeras.ipynb	View secret
8658481	Triggered	Generic High Entropy Secret	d08d3c40ee50982a8cd4a6249960286b9ddb135e	coursera_ai/AssignmentKeras.ipynb	View secret
8658482	Triggered	Bearer Token	3734c25bd6b4c968173efd033b3f7f1b54045a57	coursera_ai/week4/a3_m4_WML_TF_Train_Save_Model_publish.ipynb	View secret
8658482	Triggered	Bearer Token	3734c25bd6b4c968173efd033b3f7f1b54045a57	coursera_ai/week4/a3_m4_WML_TF_Train_Save_Model_publish.ipynb	View secret
8658482	Triggered	Bearer Token	d08d3c40ee50982a8cd4a6249960286b9ddb135e	coursera_ai/week4/a3_m4_WML_TF_Train_Save_Model_publish.ipynb	View secret
8658482	Triggered	Bearer Token	d08d3c40ee50982a8cd4a6249960286b9ddb135e	coursera_ai/week4/a3_m4_WML_TF_Train_Save_Model_publish.ipynb	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

• 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.}

[romeokienzler]

@GM33 can you please summarize your PR?

[romeokienzler]

closing since inactive