PowerShell / PowerShell/DSC

Parameter unknown property

Open
#1,370 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Enhancement Needs Triage
Dominant language
Rust
Stars
523
Forks
75
Avg merge
3d 16h
Merged PRs (30d)
24

Description

Summary of the new feature / enhancement

Currently DSC validates that a parameter or parameter file only has properties the config doc has. For example, if I have a parameter file with foo and bar but the config doc only has foo listed as a parameter, dsc will fail during validation. This request is to have a configurable value in the config doc to allow unknown parameters.

As a user I want this file so I can have a single parameter file being passed to multiple config docs.

Proposed technical implementation details (optional)

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

No files or tests are named. Start by locating the parameter and parameter-file validation entry points and the config-document schema handling. Done means a configurable config-document value allows unknown parameters while preserving validation of known parameters, with coverage for a shared parameter file used by multiple config documents.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.