Files
Homelab-manager/server/drizzle/0093_reboot_after_updates.sql
bobbanandClaude Sonnet 5.5 e4f3a54189 Restart a server after its updates, and check that it came back
An update run can name a second Semaphore playbook that restarts the server
once the updates are in and it says a restart is due. The run keeps the
maintenance window up, follows the restart, waits for the server to report
again and checks from its uptime (or its restart flag clearing) that it did
start again. A server that only needs a restart has a Restart button on the
Updates page, and a patch plan can carry the restart playbook too.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-10 23:45:52 +01:00

12 lines
995 B
SQL

ALTER TABLE `patch_plans` ADD `restart_project_id` integer;--> statement-breakpoint
ALTER TABLE `patch_plans` ADD `restart_template_id` integer;--> statement-breakpoint
ALTER TABLE `patch_plans` ADD `restart_template_name` text;--> statement-breakpoint
ALTER TABLE `update_runs` ADD `kind` text DEFAULT 'update' NOT NULL;--> statement-breakpoint
ALTER TABLE `update_runs` ADD `restart_project_id` integer;--> statement-breakpoint
ALTER TABLE `update_runs` ADD `restart_template_id` integer;--> statement-breakpoint
ALTER TABLE `update_runs` ADD `restart_template_name` text;--> statement-breakpoint
ALTER TABLE `update_runs` ADD `restart_task_id` integer;--> statement-breakpoint
ALTER TABLE `update_runs` ADD `restart_task_status` text;--> statement-breakpoint
ALTER TABLE `update_runs` ADD `restart_started_at` text;--> statement-breakpoint
ALTER TABLE `update_runs` ADD `restart_ended_at` text;--> statement-breakpoint
ALTER TABLE `update_runs` ADD `restarted` integer DEFAULT false NOT NULL;