microsoft / microsoft/OpenAPI.NET.OData

Potential breaking changes in Graph PowerShell SDK due to change/rename of tags

Open
#605 2 comments 0 reactions 0 assignees View on GitHub

A pull request for this has already been merged.

  • #642 by @timayabi2020 — merged
Dominant language
C#
Stars
240
Forks
70
Avg merge
7h 59m
Merged PRs (30d)
13

Description

The following tags are missing from the latest metadata for PowerShell.
users.Actions
users.Functions
deviceManagement.Functions
deviceManagement.Actions.

This means that if you try to slice the metadata using the above tags, the service will respond with a 404. e.g. https://devxapi-func-prod-eastus.azurewebsites.net/$openapi?tags=^users.Functions$&title=Users.Functions&openapiversion=3&style=Powershell&fileName=powershell_v2&graphVersion=v1.0&singularizeOperationIds=true.

Therefore, some paths that were assigned those tags, currently have new tags and this would potentially introduce breaking changes in the SDK.
Below is an example of before and after for one of the paths.
Before
Image

After
Image

The change will occur in terms of grouping of paths. e.g. Paths that used to appear under Users. Actions module are now appearing under Calendar module.

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 comparing the users and deviceManagement tags in the linked powershell_v2.yaml metadata with the $openapi slicing request shown in the issue, then inspect the generated path groupings. Done means the affected tags no longer return 404 and the affected paths retain compatible PowerShell SDK grouping; review linked pull request #642 for existing work.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, openapi, powershell
Domain
api, tooling
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.