Use current promoted files for blueprint launches
This commit is contained in:
@@ -416,8 +416,8 @@ CREATE TABLE IF NOT EXISTS server_creation_jobs (
|
||||
expected_map TEXT NOT NULL
|
||||
);
|
||||
|
||||
-- Launch recipes copy managed files, not credentials from the key/integration stores.
|
||||
-- Independent of the artifact library so history survives version deletion.
|
||||
-- Blueprints retain map/count selections only. The legacy column name remains
|
||||
-- compatible with older snapshot-based definitions, read as selections at runtime.
|
||||
CREATE TABLE IF NOT EXISTS server_blueprints (
|
||||
id TEXT PRIMARY KEY,
|
||||
name TEXT NOT NULL COLLATE NOCASE UNIQUE,
|
||||
@@ -436,6 +436,8 @@ CREATE TABLE IF NOT EXISTS server_launch_previews (
|
||||
deployment_id TEXT REFERENCES server_deployments(id) ON DELETE CASCADE
|
||||
);
|
||||
|
||||
-- Historical launch files survive library deletion. New launches resolve current
|
||||
-- promotions instead of replaying these snapshots; credentials stay in their stores.
|
||||
CREATE TABLE IF NOT EXISTS server_launch_recipes (
|
||||
deployment_id TEXT PRIMARY KEY REFERENCES server_deployments(id) ON DELETE CASCADE,
|
||||
recipe TEXT NOT NULL,
|
||||
|
||||
Reference in New Issue
Block a user