PowerShell / PowerShell/DSC

Support sending metadata to group/adapter resources for `securityContext`

Open
#727 0 comments 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

As a resource developer, I want to be able to design my resource to receive metadata about the operation from DSC so that I don't need to implement similar context retrieval myself. For example, if DSC can indicate the current security context, I can rely on that information for fast-failing an operation.

While I'm specifically discussing securityContext for this issue, this functionality likely holds for other metadata fields that currently exist and may be added later.

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

The issue proposes passing operation metadata, especially securityContext, to group and adapter resources, but names no files or tests. Start by locating the resource operation entry points and existing metadata handling; done means a defined and implemented way for resources to receive the requested metadata.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.