microsoft / microsoft/PowerStig
Test-DscConfiguration as part of PR checks
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 619
- Forks
- 124
- PR merge metrics
- No merged PRs in 30d
Description
There is currently no test to validate that a DSC configuration, including each DSC resource updated as part of a PR, generates a useable MOF file, before merging.
I'd like to add a test to the Azure Pipeline, which will ensure that a MOF file generated by a DSC configuration, consisting of each resource being touched by a PR, is tested using Test-DscConfiguration.
MOF files could be manually tested, but that's more time consuming and error prone.
This is to prevent situations where a DSC resource does not produce a working MOF file, despite passing the existing tests.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Azure Pipeline checks and the existing tests for DSC resources. Investigate how each resource touched by a PR generates a MOF file, then use Test-DscConfiguration to validate those files; done means the pipeline rejects unusable MOF output before merging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, powershell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100