From 881524bd5466c19875403b46915ac2ec5762b0ca Mon Sep 17 00:00:00 2001 From: BlackDex Date: Sat, 9 Oct 2021 14:16:27 +0200 Subject: [PATCH] Added DbConn to /alive healthcheck During a small discusson on Matrix it seems logical to have the /alive endpoint also check if the database connection still works. The reason for this was regarding a certificate which failed/expired while vaultwarden and the database were still up-and-running, but suddenly vaultwarden couldn't connect anymore. With this `DbConn` added to `/alive`, it will be more accurate, because of vaultwarden can't reach the database, it isn't alive. --- src/api/web.rs | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/api/web.rs b/src/api/web.rs index 9980179f..9c960c27 100644 --- a/src/api/web.rs +++ b/src/api/web.rs @@ -64,8 +64,10 @@ fn attachments(uuid: SafeString, file_id: SafeString) -> Option { NamedFile::open(Path::new(&CONFIG.attachments_folder()).join(uuid).join(file_id)).ok() } +// We use DbConn here to let the alive healthcheck also verify the database connection. +use crate::db::DbConn; #[get("/alive")] -fn alive() -> Json { +fn alive(_conn: DbConn) -> Json { use crate::util::format_date; use chrono::Utc;