PowerShell / PowerShell/DSC

Canonical properties for credentials

Open
#1,273 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Summary of the new feature / enhancement

As a user I would like canonical properties for credential fields so that resources use the same convention.

Proposed technical implementation details (optional)

Some example properties:

  • _username
  • _password
  • _token

_password and _token could be combined to be a generic that accounts for all types of secrets, maybe a _secret property.

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 names no files, tests, or entry points. Start by reviewing how credential fields are currently represented and compare them with the proposed _username, _password, _token, and _secret conventions. Done requires an agreed canonical naming scheme and a defined implementation scope.

Written by the indexing model from the issue text.

Assessment

Domain
authentication
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.