datum-configuration

Hierarchical DSC configuration data is resolved using Datum.yml to define ResolutionPrecedence across multiple stores like AllNodes, Environment, and Roles. This enables predictable, policy-driven configuration synthesis for deployments.

The best way to compute RSOP for a DSC node is by loading Datum.yml and running Get-DatumRsop. The resulting RSOP is then applied via RootConfiguration to generate the necessary MOF files.

Merge strategies like MostSpecific, hash, deep, and DeepTuple control how DSC configuration layers combine. They dictate data resolution across stores and include knockout support to override or exclude specific values.

Scenario-based overrides can be applied to tailor DSC configurations per environment and service tag. Datum supports these overrides alongside cross-domain references to ensure robust data resolution.

Multiple data stores are needed for DSC configuration when managing complex deployments across Baselines, Roles, and Environments. Datum provides a unified model to compose this multi-store data with predictable resolution precedence.

Datum supports knockout configuration values in DSC deployments, allowing specific properties to be explicitly excluded or overridden during the merge process. This ensures accurate RSOP computation across hierarchical layers.