feat: Allow access to pgx pool - BED-8082

[cweidenkeller]

Description

Add access to pgx pool to allow for easier registration of composite types

Motivation and Context

Helps resolve BED-8082

Why is this change required? What problem does it solve?

We don't have access to the pgx pool directly we need access for registering OIDs

How Has This Been Tested?

This is just an accessor.

Please describe in detail how you tested your changes.
Include details of your testing environment, and the tests you ran to
see how your change affects other areas of the code, etc.

Screenshots (optional):

Types of changes

• Chore (a change that does not modify the application functionality)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Database Migrations

Checklist:

• I have met the contributing prerequisites
  • Assigned myself to this PR
  • Added the appropriate labels
  • Associated an issue: Issues and Pull Requests README #672
  • Read the Contributing guide: https://github.com/SpecterOps/BloodHound/wiki/Contributing
• I have ensured that related documentation is up-to-date
  • Open API docs
  • Code comments (GoDocs / JSDocs)
• I have followed proper test practices
  • Added/updated tests to cover my changes
  • All new and existing tests passed

Summary by CodeRabbit

• New Features
  • Exposes direct access to the application's database connection pool, making it easier for trusted tooling or integrations to perform lower-level database operations and diagnostics.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1f8904f2-d2ba-447b-aed7-8d9dbb6118ae

📥 Commits

Reviewing files that changed from the base of the PR and between 0a8160b and 58ec95a.

📒 Files selected for processing (1)

• cmd/api/src/database/db.go

🚧 Files skipped from review as they are similar to previous changes (1)

• cmd/api/src/database/db.go

---

📝 Walkthrough

Walkthrough

Adds an exported Pool() method to BloodhoundDB that returns the internal *pgxpool.Pool instance, providing direct access to the PostgreSQL connection pool.

Changes

Database Pool Accessor

Layer / File(s)	Summary
BloodhoundDB Pool() method cmd/api/src/database/db.go	Added func (s *BloodhoundDB) Pool() *pgxpool.Pool which returns the internal pgx connection pool field. This is the only change in the file.

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description addresses the main objective but lacks concrete details in critical sections. Testing section is empty, motivation is brief, and no specific type of change is selected.	Expand 'How Has This Been Tested' with specific test details, testing environment, and confirm which type of change applies (likely 'New feature'). Clarify the motivation with more context about why pgx pool access is needed.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically summarizes the main change: exposing access to the pgx pool with a relevant ticket reference.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ 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 BED-8082

---

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]

Caution

Failed to replace (edit) comment. This is likely due to insufficient permissions or the comment being deleted.

Error details

{}