Two types in shared/core/Models look authoritative and are referenced by nothing:
Configuration.cs is a complete snake_case client-configuration model. The real one is CimianConfig in cli/managedsoftwareupdate/Models/UpdateModels.cs:9, and it is PascalCase. build/msi/config.yaml is a matching snake_case sample that no build script packages, so it reinforces the wrong shape.
CatalogItem.cs declares keys the client never deserialises — url, installer_args, requires_elevation, restart_required, metadata.
Anyone reading the source to answer "what keys are supported" will find the wrong answer first, and a config written against Configuration.cs silently does nothing. Removing both (and the orphan sample) would leave one obvious answer.
Two types in
shared/core/Modelslook authoritative and are referenced by nothing:Configuration.csis a complete snake_case client-configuration model. The real one isCimianConfigin cli/managedsoftwareupdate/Models/UpdateModels.cs:9, and it is PascalCase.build/msi/config.yamlis a matching snake_case sample that no build script packages, so it reinforces the wrong shape.CatalogItem.csdeclares keys the client never deserialises —url,installer_args,requires_elevation,restart_required,metadata.Anyone reading the source to answer "what keys are supported" will find the wrong answer first, and a config written against
Configuration.cssilently does nothing. Removing both (and the orphan sample) would leave one obvious answer.