chore(swagger): automate swagger sync to amrit-docs

[DurgaPrasad-54]

Summary by CodeRabbit

• Chores
  • Added GitHub Actions workflow to automate API documentation synchronization to documentation repository.
  • Configured swagger profile with in-memory database and application settings for documentation generation.
  • Added H2 database dependency for swagger profile support.

[coderabbitai]

Warning

Rate limit exceeded

@DurgaPrasad-54 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 15 minutes and 20 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📝 Walkthrough

Walkthrough

This pull request introduces a Swagger profile and automation for synchronizing API documentation. It adds a GitHub Actions workflow to build the API and push generated Swagger JSON to the AMRIT-Docs repository, configures an H2 in-memory database for the Swagger profile, and conditionally disables Redis and HTTP interceptor when the swagger profile is active.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow .github/workflows/swagger-json.yml	New workflow that builds the API, polls /v3/api-docs endpoint, captures the Swagger JSON, checks out the AMRIT-Docs repo, and creates a pull request with the updated API documentation.
Dependency Management pom.xml	Adds H2 database dependency with runtime scope for in-memory database support in Swagger profile.
Spring Configuration Profile Exclusions src/main/java/com/iemr/ecd/config/HttpInterceptorConfig.java, src/main/java/com/iemr/ecd/config/RedisConfig.java	Adds @Profile("!swagger") annotation to both classes to exclude these configurations when the swagger profile is active.
Swagger Profile Configuration src/main/resources/application-swagger.properties	New configuration file for the Swagger profile with H2 in-memory database, disabled Redis, CORS settings, and placeholder values for security-related properties.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~22 minutes

Poem

🐰 A workflow springs to life so bright,
Swagger docs in automated flight,
H2 in memory, profiles aligned,
Redis and interceptors left behind,
Documentation synced with care—hop, hop, hooray! 🎉

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: adding automation for syncing Swagger documentation to the AMRIT-Docs repository via a GitHub Actions workflow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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: 1

🤖 Fix all issues with AI agents

In `@src/main/resources/application-swagger.properties`:
- Line 24: The jwt.secret property value contains a leading space; update the
property key jwt.secret so its value has no leading or trailing whitespace
(change " JWT_SECRET" to "JWT_SECRET") to ensure the secret is read correctly by
the application (verify trim or no surrounding quotes if any).

🧹 Nitpick comments (1)

.github/workflows/swagger-json.yml (1)

37-56: Consider adding an initial delay before polling.

Spring Boot applications typically take 10-30 seconds to start. Adding an initial sleep before the polling loop could reduce unnecessary failed attempts and improve reliability.

Proposed improvement

       - name: Wait for API & fetch Swagger
         run: |
+          echo "Waiting for Spring Boot to initialize..."
+          sleep 15
           for i in {1..30}; do
             CODE=$(curl --connect-timeout 2 --max-time 5 -s -o swagger_raw.json -w "%{http_code}" http://localhost:9090/v3/api-docs || true)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud