feat: add appName field to volume_backup schema and enhance deployment volume backup functionality

- Introduced a new appName column in the volume_backup table to improve application identification.
- Updated the volume backup schema to ensure appName is a required field.
- Enhanced the deployment service to support volume backup creation, integrating appName into the deployment process.
- Added validation for volume backup creation to ensure proper handling of appName and related data.

packages/server/src/db/schema/deployment.ts

@@ -188,6 +188,17 @@ export const apiCreateDeploymentSchedule = schema
 		scheduleId: z.string().min(1),
 	});
 
+export const apiCreateDeploymentVolumeBackup = schema
+	.pick({
+		title: true,
+		status: true,
+		logPath: true,
+		description: true,
+	})
+	.extend({
+		volumeBackupId: z.string().min(1),
+	});
+
 export const apiFindAllByApplication = schema
 	.pick({
 		applicationId: true,

packages/server/src/db/schema/volume-backups.ts

@@ -13,6 +13,7 @@ import { postgres } from "./postgres";
 import { mariadb } from "./mariadb";
 import { destinations } from "./destination";
 import { deployments } from "./deployment";
+import { generateAppName } from "./utils";
 
 export const volumeBackups = pgTable("volume_backup", {
 	volumeBackupId: text("volumeBackupId")
@@ -23,6 +24,9 @@ export const volumeBackups = pgTable("volume_backup", {
 	volumeName: text("volumeName").notNull(),
 	prefix: text("prefix").notNull(),
 	serviceType: serviceType("serviceType").notNull().default("application"),
+	appName: text("appName")
+		.notNull()
+		.$defaultFn(() => generateAppName("volumeBackup")),
 	serviceName: text("serviceName"),
 	turnOff: boolean("turnOff").notNull().default(false),
 	cronExpression: text("cronExpression").notNull(),