[IL-84]Environments

[voltwatt]

Adding environment profiles to pom.xml

[Sunagatov]

Reviewed

[Sunagatov]

How does this unit test can help us?

[voltwatt]

The test quickly validates that the application container is running and the web server is reachable, so we know we can start coding against it. While the test is simple, it can catch glaring issues like if the server isn't running or is misconfigured, which saves debugging time later. Although this is a basic test, it serves as a foundation for more complex health checks in the future.

[gitguardian]

⚠️ GitGuardian has uncovered 5 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	Secret	Commit	Filename
-	Generic High Entropy Secret	7cbe425	src/main/resources/application.yaml	View secret
-	Generic High Entropy Secret	0a05203	src/main/resources/application.properties	View secret
-	Generic High Entropy Secret	41ef0d4	src/main/resources/application.properties	View secret
-	Generic High Entropy Secret	7cbe425	src/main/resources/application.properties	View secret
-	Generic High Entropy Secret	0a05203	src/main/resources/application.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

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

---

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

Our GitHub checks need improvements? Share your feedbacks!</sup>