Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

DirectoryObjects: drop the publicKeyInfrastructureRoot tag from the module mapping (v2)

Open Beginner friendly
#3,752 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
84/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
powershell
Domain
build-system, tooling

Research direction

Start in config/ModulesMapping.jsonc and src/DirectoryObjects/DirectoryObjects.md; compare the DirectoryObjects mapping with identity.DirectoryManagement and the v1.0 rows in MgCommandMetadata.json. Remove the v2 tag and 17 directives, then regenerate DirectoryObjects; done when the generated diff is empty apart from those directive removals.

Written by the indexing model from the issue text.

Description

While fixing a duplicate-generation problem in v3 (#3733), we found that the DirectoryObjects entry in config/ModulesMapping.jsonc on main still claimsdirectory.publicKeyInfrastructureRoot, but the module never actually ships that surface. The cmdlets get generated and then deleted again by 17 remove directives in src/DirectoryObjects/DirectoryObjects.md. The real owner is identity.DirectoryManagement - it has all 18 publicKeyInfrastructure files on main across v1.0 and beta, and every v1.0 row in MgCommandMetadata.json points there.

So today the tag just creates work that directives throw away, and the mapping says the wrong module owns the surface. v3 already removed the tag on its side; this issue is to do the same on v2, per the review discussion on #3733.

Suggested fix:

  1. Remove directory.publicKeyInfrastructureRoot from the DirectoryObjects entry in config/ModulesMapping.jsonc.
  2. Delete the 17 dead PublicKeyInfrastructure remove directives from src/DirectoryObjects/DirectoryObjects.md.
  3. Regenerate DirectoryObjects - the diff should be empty apart from the directives, which confirms the tag was producing nothing.
Dominant language
C#
Stars
898
Forks
230
Avg merge
2d 5h
Merged PRs (30d)
31

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.

More from microsoftgraph/msgraph-sdk-powershell

All issues in microsoftgraph/msgraph-sdk-powershell

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.