The expiry date is now optional: no date means the secret never expires, gets the status "no expiry" and never raises an alert or reminder. The Secrets form has a "Never expires" checkbox. Certificates checked against a host keep their live expiry and can't be set to never expire. Migration 0016 makes secrets.expiry_date nullable. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
21 lines
1.1 KiB
SQL
21 lines
1.1 KiB
SQL
PRAGMA foreign_keys=OFF;--> statement-breakpoint
|
|
CREATE TABLE `__new_secrets` (
|
|
`id` integer PRIMARY KEY AUTOINCREMENT NOT NULL,
|
|
`name` text NOT NULL,
|
|
`type` text DEFAULT 'generic' NOT NULL,
|
|
`description` text,
|
|
`expiry_date` text,
|
|
`warn_days` integer DEFAULT 30 NOT NULL,
|
|
`notes` text,
|
|
`check_host` text,
|
|
`check_port` integer,
|
|
`last_checked_at` text,
|
|
`last_check_error` text,
|
|
`created_at` text DEFAULT (current_timestamp) NOT NULL,
|
|
`updated_at` text DEFAULT (current_timestamp) NOT NULL
|
|
);
|
|
--> statement-breakpoint
|
|
INSERT INTO `__new_secrets`("id", "name", "type", "description", "expiry_date", "warn_days", "notes", "check_host", "check_port", "last_checked_at", "last_check_error", "created_at", "updated_at") SELECT "id", "name", "type", "description", "expiry_date", "warn_days", "notes", "check_host", "check_port", "last_checked_at", "last_check_error", "created_at", "updated_at" FROM `secrets`;--> statement-breakpoint
|
|
DROP TABLE `secrets`;--> statement-breakpoint
|
|
ALTER TABLE `__new_secrets` RENAME TO `secrets`;--> statement-breakpoint
|
|
PRAGMA foreign_keys=ON; |