azure-powershell
azure-powershell copied to clipboard
Fixed required parameters missing for *-AzPrivateEndpointConnection.
trafficstars
Description
Dynamic parameter PrivateLinkResourceType is required for the following cmdlets:
Get-AzPrivateEndpointConnectionSet-AzPrivateEndpointConnectionRemove-AzPrivateEndpointConnectionApprove-AzPrivateEndpointConnectionDeny-AzPrivateEndpointConnection
Updated help docs for these cmdlets as well. [Fixed #18655]
Checklist
- [x] Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:
- SHOULD select appropriate branch. Cmdlets from Autorest.PowerShell should go to
generationbranch. - SHOULD make the title of PR clear and informative, and in the present imperative tense.
- SHOULD update
ChangeLog.mdfile(s) appropriately- For any service, the
ChangeLog.mdfile can be found atsrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md - A snippet outlining the change(s) made in the PR should be written under the
## Upcoming Releaseheader in the past tense. Add changelog in description section if PR goes intogenerationbranch. - Should not change
ChangeLog.mdif no new release is required, such as fixing test case only.
- For any service, the
- SHOULD have approved design review for the changes in this repository (Microsoft internal only) with following situations
- Create new module from the scratch
- Create new resource types which are not easy to conform to Azure PowerShell Design Guidelines
- Create new resource type which name doesn't use module name as prefix
- Have design question before implementation
- SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
- SHOULD have proper test coverage for changes in pull request.
- SHOULD NOT introduce breaking changes in Az minor release except preview version.
- SHOULD NOT change version of module in pull request
/azp run azure-powershell - powershell-core
Azure Pipelines successfully started running 1 pipeline(s).
/azp run azure-powershell - powershell-core
Azure Pipelines successfully started running 1 pipeline(s).