Struct YamlProjectRegistry 

pub struct YamlProjectRegistry;

A ProjectRegistry backed by projects.yml in the user’s config directory (~/.config/muster/projects.yml on Linux). A project’s config path may begin with ~; ambiguous legacy relative paths are rejected.

Trait Implementations

impl Default for YamlProjectRegistry

fn default() -> YamlProjectRegistry

Returns the “default value” for a type.

impl ProjectRegistry for YamlProjectRegistry

fn projects(&self) -> Result<Vec<Project>, ConfigError>

The registered projects, in file order. A missing registry yields an empty list rather than an error.

fn workspace(&self, config_path: &Path) -> Result<WorkspaceConfig, ConfigError>

Loads the workspace configuration at config_path.

fn workspace_exists(&self, config_path: &Path) -> bool

Whether a workspace config already exists at config_path.

fn save(&self, projects: &[Project]) -> Result<(), ConfigError>

Persists the full project list, replacing the registry file.

fn save_workspace( &self, config_path: &Path, config: &WorkspaceConfig, ) -> Result<(), ConfigError>

Persists config to config_path, creating parent directories.

fn create_workspace( &self, config_path: &Path, config: &WorkspaceConfig, ) -> Result<bool, ConfigError>

Creates the workspace at config_path only when nothing exists there. Returns whether this call created the file. The default checks then writes; a filesystem-backed adapter should override it with an atomic exclusive create so a concurrent creation is never overwritten.

fn update_projects( &self, update: &mut dyn FnMut(Vec<Project>) -> Vec<Project>, ) -> Result<(), ConfigError>

Applies update to the project list under the registry’s exclusive lock where the implementation provides one, so concurrent mutations serialize instead of losing writes.

fn update_workspace( &self, config_path: &Path, update: &mut dyn FnMut(WorkspaceConfig) -> WorkspaceConfig, ) -> Result<(), ConfigError>

Reads the workspace at config_path, applies update, and writes it back as a single operation, so concurrent updates to the same project (for example two muster run invocations) cannot lose each other. The default is an unlocked read-modify-write; a filesystem-backed adapter should override this to hold an exclusive lock across the whole sequence.