fetch

[praveenKDass]

Summary by CodeRabbit

• New Features

  • Added new endpoints to support internal link retrieval operations across services, enabling additional query capabilities.

• Chores

  • Package version updates: elevate-project (1.1.51 → 1.1.52), elevate-survey (1.0.20 → 1.0.21).

[coderabbitai]

Walkthrough

This PR adds two new internal API routes (fetchLinkInternal with and without ID parameter) to both the project and survey services, and increments version numbers in both packages. No existing logic or dependencies are modified.

Changes

Cohort / File(s)	Summary
Route Additions elevate-project/constants/routes.js, elevate-survey/constants/routes.js	Added two new GET route entries per file for /solutions/fetchLinkInternal and /solutions/fetchLinkInternal/:id, mirroring existing route structure and targeting respective services (project, survey).
Version Bumps elevate-project/package.json, elevate-survey/package.json	Incremented versions: elevate-project from 1.1.51 to 1.1.52, and elevate-survey from 1.0.20 to 1.0.21.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

The changes are homogeneous, configuration-driven additions with no logic modifications. The new routes follow an identical pattern applied consistently across two services, requiring minimal scrutiny beyond verifying naming consistency and route correctness.

Possibly related PRs

• routes updated for org-policy in project-service #344: Also adds new route entries to elevate-project/constants/routes.js following the same pattern.
• survey library and orgPolicies routes added #347: Also adds new route entries to elevate-survey/constants/routes.js with identical structural approach.
• elevate-survey-observation npm package updated #357: Modifies elevate-survey/constants/routes.js with additional route entries using the same configuration pattern.

Suggested reviewers

• VISHNUDAS-tunerlabs

Poem

🐰 New routes hop into place, fetchLinkInternal takes the race,
With IDs and without, through project and survey routes,
Versions climb higher still, a tiny bump with graceful skill,
Configuration flows so neat, making the API suite complete! 🚀

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The title “fetch” is too broad and nonspecific to convey the primary change of adding new internal fetchLink routes for project and survey services. It does not describe the actual routes added or the package version updates.	Consider updating the title to clearly reflect the main change, for example “Add fetchLinkInternal routes for project and survey services” or similar phrasing that specifies the new functionality.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fetchLink_routesAdded

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1e2b8b5 and 20afc4b.

📒 Files selected for processing (4)

• elevate-project/constants/routes.js (1 hunks)
• elevate-project/package.json (1 hunks)
• elevate-survey/constants/routes.js (1 hunks)
• elevate-survey/package.json (1 hunks)

🔇 Additional comments (4)

elevate-project/package.json (1)

3-3: LGTM! Version bump is appropriate.

The patch version increment aligns with the addition of new internal API routes.

elevate-survey/package.json (1)

3-3: LGTM! Version bump is appropriate.

The patch version increment aligns with the addition of new internal API routes.

elevate-project/constants/routes.js (1)

1126-1147: Ensure fetchLinkInternal handlers exist and enforce internal-only access

• Confirm implementations for /project/v1/solutions/fetchLinkInternal (with and without :id) are present
• Verify they enforce proper authentication/authorization (e.g., IP allowlisting or service-to-service tokens)
• Ensure these routes aren’t exposed to unauthorized clients and document their internal use

elevate-survey/constants/routes.js (1)

201-222: Verify internal route security
These route entries are proxy definitions to the survey service—actual access controls live in your API gateway or downstream microservice. Confirm that:

• /survey/v1/solutions/fetchLinkInternal (with/without :id) endpoints require internal-only auth (IP allow-listing, mTLS, or service-to-service tokens)
• They’re not exposed to public clients
• Documentation clearly distinguishes fetchLink vs fetchLinkInternal

---

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