You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Experimental support for DSC v3 processing (#5252)
## Change
Adds experimental support for DSC v3 processing of configurations. When
enabled, one can use DSC v3 instead of PowerShell DSC v2 by setting
their processor to `dscv3` for the configuration like:
```yaml
$schema: https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2023/08/config/document.json
metadata:
winget:
processor: dscv3
resources:
<continue with schema 0.3 resource definitions>
```
This is currently on-par with DSC v2 in terms of functionality, except
for 2 things:
1. It does not attempt to ensure dsc.exe is present. It will find and
use the preview MSIX packaged version of dsc.exe (Store ID:
`9PCX3HX4HZ0Z`) if installed. Otherwise, you can specify the
`--processor-path` to dsc.exe.
2. Resources for DSC v3 must be present on the system. There is not
currently any mechanism to find and install new resources, as the
paradigm is that they are part of the configurable item. There is no
special handling of DSC v2 resources in the configuration; that could
potentially come later.
Also makes 0.3 schema not experimental and fixes configuration history
for environments.
Copy file name to clipboardExpand all lines: doc/Settings.md
+3-14Lines changed: 3 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -355,25 +355,14 @@ You can enable the feature as shown below.
355
355
},
356
356
```
357
357
358
-
### configuration03
358
+
### dsc3
359
359
360
-
This feature enables the configuration schema 0.3.
360
+
This feature enables support for DSC v3 integration.
361
361
You can enable the feature as shown below.
362
362
363
363
```json
364
364
"experimentalFeatures": {
365
-
"configuration03": true
366
-
},
367
-
```
368
-
369
-
### configureSelfElevate
370
-
371
-
This feature enables configure commands to request elevation as needed.
372
-
Currently, this means that properly attributed configuration units (and only those) will be run through an elevated process while the rest are run from the current context.
0 commit comments