microsoftgraph / microsoftgraph/msgraph-sdk-powershell

No cmdlet corresponding to `POST /deviceManagement/reports/cachedReportConfigurations`

Open
#2,610 1 comment 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

goodfirstissue Status: Needs Investigation
Dominant language
C#
Stars
898
Forks
230
Avg merge
2d 5h
Merged PRs (30d)
31

Description

Describe the bug
Commandlet for API endpoint POST /deviceManagement/reports/cachedReportConfigurations (Graph API endpoint documented here) doesn't exist.

To Reproduce
Steps to reproduce the behavior:

  1. Try to run New-MgBetaDeviceManagementReportCachedReportConfiguration
  2. Receive error: New-MgBetaDeviceManagementReportCachedReportConfiguration: The term 'New-MgBetaDeviceManagementReportCachedReportConfiguration' is not recognized as a name of a cmdlet, function, script file, or executable program.
  3. Run Get-Command *-MgBetaDeviceManagementReportCachedReportConfiguration - only the Get- cmdlet exists.

Expected behavior
I would expect a commandlet would exist to provide this functionality - for example, Get-MgBetaDeviceManagementReportCachedReportConfiguration (the GET equivalent) does exist.

Debug Output
N/A

Module Version
2.14.1

Environment Data

Name                           Value
----                           -----
PSVersion                      7.3.10
PSEdition                      Core
GitCommitId                    7.3.10
OS                             Microsoft Windows 10.0.19045
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Screenshots
N/A

Additional context
The API endpoint does appear to be listed in the OpenAPI specification for Reports.yml, so I'm not sure why the corresponding commandlet isn't generated during builds.

Thank you!

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.