Skip to content

feat: log database type when connecting to config store#3724

Draft
impoiler wants to merge 1 commit into
devfrom
05-25-chore_added_connecting_to_db_log_on_server_initialization
Draft

feat: log database type when connecting to config store#3724
impoiler wants to merge 1 commit into
devfrom
05-25-chore_added_connecting_to_db_log_on_server_initialization

Conversation

@impoiler
Copy link
Copy Markdown
Contributor

@impoiler impoiler commented May 25, 2026

Summary

Adds a log message when the config store initializes a database connection, making it easier to observe which database backend is being used at startup.

Changes

  • A log line is emitted at the Info level before the database type switch, reporting the configured store type (e.g., SQLite) when a connection is being established.

Type of change

  • Bug fix
  • Feature
  • Refactor
  • Documentation
  • Chore/CI

Affected areas

  • Core (Go)
  • Transports (HTTP)
  • Providers/Integrations
  • Plugins
  • UI (React)
  • Docs

How to test

go test ./...

Start the application with a configured config store and verify that a log line similar to the following appears on startup:

connecting to sqlite database

Screenshots/Recordings

N/A

Breaking changes

  • Yes
  • No

Related issues

N/A

Security considerations

The log message only exposes the database type (e.g., sqlite), not any connection credentials or sensitive configuration values.

Checklist

  • I read docs/contributing/README.md and followed the guidelines
  • I added/updated tests where appropriate
  • I updated documentation where needed
  • I verified builds succeed (Go and UI)
  • I verified the CI pipeline passes locally if applicable

@impoiler impoiler changed the title chore: added connecting to db log on server initialization feat: log database type when connecting to config store May 25, 2026
@impoiler impoiler self-assigned this May 25, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 25, 2026

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1f12ff93-836c-41c7-a07c-0e2e2fc2746c

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

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 05-25-chore_added_connecting_to_db_log_on_server_initialization

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

@impoiler impoiler force-pushed the 05-25-chore_added_connecting_to_db_log_on_server_initialization branch from 07e9554 to 4446e5d Compare May 26, 2026 04:55
@impoiler impoiler changed the base branch from main to graphite-base/3724 May 26, 2026 05:53
@impoiler impoiler force-pushed the graphite-base/3724 branch from 00f2e17 to b2ca296 Compare May 26, 2026 05:53
@impoiler impoiler force-pushed the 05-25-chore_added_connecting_to_db_log_on_server_initialization branch from 4446e5d to b095986 Compare May 26, 2026 05:53
@impoiler impoiler changed the base branch from graphite-base/3724 to dev May 26, 2026 05:53
@impoiler impoiler force-pushed the 05-25-chore_added_connecting_to_db_log_on_server_initialization branch from b095986 to 33dbbd7 Compare May 26, 2026 07:50
@impoiler impoiler mentioned this pull request May 26, 2026
18 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant