pub struct CreateWorkspaceFork {
pub id: String,
pub name: String,
pub color: Option<String>,
pub forked_datatables: Option<Vec<CreateWorkspaceForkForkedDatatablesInner>>,
pub shared_ducklakes: Option<Vec<String>>,
pub shared_storages: Option<Vec<String>>,
pub is_dev_workspace: Option<bool>,
pub lock_prod_deploy: Option<bool>,
pub lock_prod_forking: Option<bool>,
pub copy_members: Option<bool>,
pub dev_workspace_label: Option<DevWorkspaceLabel>,
}Fields§
§id: String§name: String§color: Option<String>§forked_datatables: Option<Vec<CreateWorkspaceForkForkedDatatablesInner>>Lake names the fork SHARES with the parent (reads and writes the parent’s lake directly). Every lake not listed gets the default isolated fork namespace with read-defer to the parent.
Workspace storages the fork SHARES with the parent (_default_ for the primary one): it reads and writes the parent’s objects directly. Every storage not listed is isolated: the fork writes under its own prefix and reads through to the parent’s objects.
is_dev_workspace: Option<bool>Create the fork as a persistent dev workspace (id not required to carry the wm-fork- prefix; at most one per parent)
lock_prod_deploy: Option<bool>When creating a dev workspace, lock the parent (prod) against direct deployment
lock_prod_forking: Option<bool>When creating a dev workspace, prevent forking the parent (prod)
copy_members: Option<bool>Copy the parent’s members (users + group memberships) into the fork so the team can work in it
dev_workspace_label: Option<DevWorkspaceLabel>Environment label for the dev workspace: its badge text and the branch it deploys to. Ignored for non-dev forks. Omitted defaults to ‘dev’