PowerShell / PowerShell/DSC

differingProperties always propagated on adapter resource

Open
#849 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Bug Need-Review
Dominant language
Rust
Stars
523
Forks
75
Avg merge
3d 16h
Merged PRs (30d)
24

Description

Prerequisites
  • Write a descriptive title.
  • Make sure you are able to repro it on the latest version
  • Search the existing issues.
Summary

When writing the docs for #848, I noticed that the differingProperties are always being propagated. For example, executing the following:

$instance = @{
    Name        = 'Spooler'
    StartupType = 'Automatic'
} | ConvertTo-Json

dsc resource test --resource PSDesiredStateConfiguration/Service --input $instance

Returns the desiredState equals true. I would expect the differingProperties to be empty. Instead, both Name and StartupType are returned.

Image

Steps to reproduce

See description

Expected behavior
Return `differingProperties: []`
Actual behavior
Returns both properties
Error details

Environment data
Name                           Value
----                           -----
PSVersion                      5.1.19041.5848
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.5848
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
Version

dsc 3.1.0-preview.6

Visuals

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the dsc resource test command with the PSDesiredStateConfiguration/Service adapter resource and inspect how differingProperties is produced. Done means matching properties no longer appear in that list and a regression test covers the reported input.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell, rust
Domain
backend, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.