-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Fixed Ambiguous Positional Argument for #23888
Fixed Ambiguous Positional Argument for #23888
Conversation
️✔️Az.Accounts
️✔️Az.Network
️✔️Az.Websites
|
Thank you for your contribution Marty-Me! We will review the pull request and get back to you soon. |
@microsoft-github-policy-service agree |
287b5fd
to
7c1f9bf
Compare
@@ -73,7 +73,7 @@ public class NewAzureWebAppSlotCmdlet : WebAppBaseClientCmdLet | |||
[ValidateNotNullOrEmpty] | |||
public string AseName { get; set; } | |||
|
|||
[Parameter(Position = 9, Mandatory = false, HelpMessage = "Resource group of Application Service environment")] | |||
[Parameter(Position = 10, Mandatory = false, HelpMessage = "Resource group of Application Service environment")] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updating the position of a paramter will cause breaking changes. We need to follow the breaking change process.
To the author of the pull request, |
…Marty-Me/azure-powershell into fix/ambiguous-paramter-position
/azp run azure-powershell - security-tools |
Azure Pipelines successfully started running 1 pipeline(s). |
… fix/ambiguous-paramter-position
/azp run azure-powershell - security-tools |
Azure Pipelines successfully started running 1 pipeline(s). |
Description
New-AzWebAppSlot had the same configured Position for two different arguments, resulting in an
AmbiguousPositionalParameterNoName
error. This PR configures one of the two parameters with overlapping position to use the next one.Mandatory Checklist
Please choose the target release of Azure PowerShell
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.md
and reviewed the following information:ChangeLog.md
file(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
.## Upcoming Release
header in the past tense.ChangeLog.md
if no new release is required, such as fixing test case only.