Skip to content

feat(webapp): set application_name on prisma connections#3348

Merged
nicktrn merged 1 commit intomainfrom
feat/prisma-application-name
Apr 8, 2026
Merged

feat(webapp): set application_name on prisma connections#3348
nicktrn merged 1 commit intomainfrom
feat/prisma-application-name

Conversation

@nicktrn
Copy link
Copy Markdown
Collaborator

@nicktrn nicktrn commented Apr 8, 2026

Sets application_name on the Prisma writer and replica connection strings using the existing SERVICE_NAME env var, so DB load can be attributed by service.

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Apr 8, 2026

⚠️ No Changeset found

Latest commit: ebfdd05

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 8, 2026

Walkthrough

This pull request adds database connection configuration and documentation. A new changelog file is created to document an improvement to the Prisma database connection setup. The webapp database configuration in db.server.ts is modified to set the application_name parameter from env.SERVICE_NAME on both the primary database connection client and the read-replica connection client, enabling database load attribution to originating services.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Description check ⚠️ Warning The pull request description is minimal and lacks required template sections like Checklist, Testing, and Changelog details. Add the missing template sections including a checklist confirmation, detailed testing steps, and a proper changelog entry to meet repository standards.
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (1 passed)
Check name Status Explanation
Title check ✅ Passed The title 'feat(webapp): set application_name on prisma connections' directly and accurately summarizes the main change in the changeset.

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

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/prisma-application-name

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

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

Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.

Open in Devin Review

@nicktrn nicktrn added the ready label Apr 8, 2026
@nicktrn
Copy link
Copy Markdown
Collaborator Author

nicktrn commented Apr 8, 2026

ready

@nicktrn nicktrn changed the title feat(webapp): set application_name on prisma connections from SERVICE_NAME feat(webapp): set application_name on prisma connections Apr 8, 2026
@nicktrn nicktrn enabled auto-merge (squash) April 8, 2026 21:10
@nicktrn nicktrn merged commit bd41bb2 into main Apr 8, 2026
41 checks passed
@nicktrn nicktrn deleted the feat/prisma-application-name branch April 8, 2026 21:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants