DSC v3 resource for PowerShell configuration file #25487
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/azp run PowerShell-Windows-Packaging-CI, PowerShell-CI-linux-packaging |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run PowerShell-Windows-Packaging-CI, PowerShell-CI-linux-packaging |
|
Azure Pipelines successfully started running 2 pipeline(s). |
iSazonov
reviewed
May 1, 2025
| "-NonInteractive", | ||
| "-NoProfile", | ||
| "-Command", | ||
| "./pwsh.resource.ps1 Get" |
There was a problem hiding this comment.
What if we run the pwsh not from PSHome directory? I mean OS current directory != PSHome.
Maybe convert pwsh.resource.ps1 to regular module and distribute like other in-box modules (Microsoft.PowerShell.Utility and etc.)?
|
This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 15 days. It will be closed if no further activity occurs within 10 days of this comment. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
This pull request introduces a new Desired State Configuration (DSC) resource for PowerShell, along with necessary updates to include the resource in the build process. The changes add support for managing PowerShell configurations through DSC by defining a JSON schema and implementing corresponding PowerShell scripts. Below are the key changes grouped by theme:
Addition of DSC Resource for PowerShell
pwsh.dsc.resource.json, which defines the schema, operations (Get,Set,Export), and configuration properties for managing PowerShell settings. This includes support for features like script execution policies, logging configurations, and transcription settings.pwsh.resource.ps1, to implement the functionality for theGet,Set, andExportoperations. This script validates input, manages configuration files, and handles errors gracefully.Integration into Build Process
powershell-unix.csprojto include the new DSC resource files (pwsh.dsc.resource.jsonandpwsh.resource.ps1) in the build output.powershell-win-core.csprojto include the same DSC resource files in the build output for the Windows platform.PR Context
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright header