datum-configuration

Coordinate hierarchical DSC configuration data across layers and environments.

11|1|Updated Mar 27, 2026

Search Tags:#configuration #merge #scenario #datum #hierarchy #dsc #rsop

Ready to run

npx skills add https://github.com/raandree/CopilotAtelier --skill datum-configuration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: datum-configuration
Source: https://github.com/raandree/CopilotAtelier/tree/main/Skills/datum-configuration
Command: npx skills add https://github.com/raandree/CopilotAtelier --skill datum-configuration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Datum provides a unified model to compose and resolve configuration data for DSC deployments across multiple layers, enabling predictable, policy-driven configurations.

Core Features & Use Cases

Hierarchical data composition with Datum.yml, ResolutionPrecedence, and multiple stores (AllNodes, Environment, Roles, Baselines, etc.).
RSOP computation and merging strategies (MostSpecific, hash, deep, DeepTuple) with knockout support.
Scenario-based overrides and cross-domain references to tailor configurations per environment and service tag.

Quick Start

Activate Datum by loading Datum.yml and running Get-DatumRsop for a node, then apply the RSOP via RootConfiguration to generate MOF files.

Frequently Asked Questions about datum-configuration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I resolve hierarchical DSC configuration data across multiple environments?▼

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.

What's the best way to compute RSOP for a DSC node?▼

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.

How do merge strategies work when combining DSC configuration layers?▼

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.

Can I apply scenario-based overrides to DSC configurations?▼

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.

When do I need multiple data stores for DSC configuration?▼

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.

Does Datum support knockout configuration values in DSC deployments?▼

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.