[!NOTE] This repo isn't accepting code contributions. It's public and open source to show progress and enable feedback. Once we're at a feature complete state, we can start taking code contributions.
DSCv3 is the latest iteration of Microsoft's Desired State Configuration platform. DSCv3 is an open source command line application that abstracts the management of software components declaratively and idempotently. DSCv3 runs on Linux, macOS, and Windows without any external dependencies.
With DSCv3, you can:
This project is the next generation of DSC and leverages the PSDesiredStateConfiguration module to maintain compatibility with existing PowerShell based resources.
DSCv3 differs from PowerShell DSC in a few important ways:
Importantly, while DSCv3 represents a major change to the DSC platform, DSCv3 is able to invoke PowerShell DSC Resources, including script-based and class-based DSC Resources, as they exist today. The configuration documents aren't compatible, but all published PowerShell DSC Resources are. You can use PowerShell DSC resources in DSCv3 with both Windows PowerShell and PowerShell.
To install DSC v3:
PATH
.If you're new to DSC or configuration management, we recommend reviewing the documentation.
If you're already familiar with DSC or just want to start experimenting with v3, we recommend reviewing the Samples repository and the accompanying tutorial site. The Samples repo is ready to accept Pull Requests, which is a great way to contribute while v3 is in early phases of development.
DSCv3 is a platform tool that abstracts the concerns for defining and invoking resources. Higher order tools, like Azure Machine Configuration, Azure Automanaged VM, and WinGet are early partners for DSCv3 as orchestration agents.
DSCv3 uses JSON schemas to define the structure of resources, configuration documents, and the outputs that DSCv3 returns. These schemas make it easier to integrate DSCv3 with other tools, because they standardize and document how to interface with DSCv3.
Please see our Code of Conduct before participating in this project.
For any security issues, please see our Security Policy.