Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update-AzADApplication parameter web not in custom but is in internal #16750

Closed
ErwinWiegman opened this issue Jan 4, 2022 · 0 comments · Fixed by #17849
Closed

Update-AzADApplication parameter web not in custom but is in internal #16750

ErwinWiegman opened this issue Jan 4, 2022 · 0 comments · Fixed by #17849
Assignees
Labels
AAD AzAd cmdlets in Az.Resources customer-reported feature-request This issue requires a new behavior in the product in order be resolved.

Comments

@ErwinWiegman
Copy link

ErwinWiegman commented Jan 4, 2022

Description

In the documentation you can modify EnableIdTokenIssuance on the web object. But there is no web parameter to update the new setting with. In the /custom/Update-AzADApplication the web parameter is missing, but in the /internal/Update-AzADApplication there is a parameter ${web} is there.

At this point we are not able to set Web items. So this looks like someone forgot to add the parameter. (latest Az.powershell 7.0.0)

Link to custom
https://github.com/Azure/azure-powershell/blob/7078f728c926d2ed7673a4768bc7f19457156dcb/src/Resources/MSGraph.Autorest/custom/Update-AzADApplication.ps1

Link to internal
https://github.com/Azure/azure-powershell/blob/7078f728c926d2ed7673a4768bc7f19457156dcb/src/Resources/MSGraph.Autorest/internal/Update-AzADApplication.ps1

Issue script & Debug output

$DebugPreference='Continue'
Update-AzADApplication -Web
Update-AzADApplication: Parameter cannot be processed because the parameter name 'Web' is ambiguous. Possible matches include: -HomePage -ReplyUrl.

Environment data

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

Module versions

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     2.2.1      Az.Accounts                         {Add-AzEnvironment, Clear-AzContext, Clear-AzDefault, Connect-AzAccount...}

Error output

PS C:\Users\beheerder> Update-AzADApplication -Web
Update-AzADApplication: Parameter cannot be processed because the parameter name 'Web' is ambiguous. Possible matches include: -HomePage -ReplyUrl.
@ErwinWiegman ErwinWiegman added bug This issue requires a change to an existing behavior in the product in order to be resolved. needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Jan 4, 2022
@ghost ghost added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Jan 4, 2022
@dingmeng-xue dingmeng-xue added the AAD AzAd cmdlets in Az.Resources label Jan 5, 2022
@VeryEarly VeryEarly linked a pull request Apr 19, 2022 that will close this issue
8 tasks
@dingmeng-xue dingmeng-xue added feature-request This issue requires a new behavior in the product in order be resolved. and removed bug This issue requires a change to an existing behavior in the product in order to be resolved. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Apr 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AAD AzAd cmdlets in Az.Resources customer-reported feature-request This issue requires a new behavior in the product in order be resolved.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants