feat : enable native build

[rajadilipkolli]

No description provided.

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (2)

• .github/workflows/config-server.yml is excluded by !**/*.yml
• config-server/pom.xml is excluded by !**/*.xml

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The recent changes include disabling Spring Cloud refresh in the application.properties file within the config-server project. Additionally, the GitHub Actions workflow for config-server has been modified to run a Maven command with the -Pnative profile when the GitHub reference is not 'refs/heads/main'.

Changes

File	Change Summary
config-server/src/main/resources/application.properties	Disabled Spring Cloud refresh by setting spring.cloud.refresh.enabled=false.
.github/workflows/config-server.yml	Updated workflow condition to trigger on branches other than main and added Maven -Pnative profile.

Poem

In the server's heart, a change so grand,
Spring's refresh now takes a stand,
A workflow shift from branch to branch,
With Maven's native, we take our chance.
Code evolves, as seasons flow,
With each commit, new seeds we sow. 🌱

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch config-server-native-build

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 679714c and db8a6a5.

Files selected for processing (1)

• config-server/src/main/resources/application.properties (1 hunks)

Files skipped from review due to trivial changes (1)

• config-server/src/main/resources/application.properties

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between db8a6a5 and 49233ef.

Files selected for processing (1)

• .github/workflows/config-server.yml (1 hunks)

Additional comments not posted (2)

.github/workflows/config-server.yml (2)

47-47: Conditional statement change approved.

The conditional statement now correctly triggers the job for branches other than the main branch.

---

53-53: Maven command change approved.

The Maven command now includes the -Pnative profile, which is necessary for native image generation with GraalVM.

[gitguardian]

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

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
8725266	Triggered	Generic High Entropy Secret	e272881	api-gateway/src/main/resources/application.yml	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 secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
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.}