[Express Route] IPv6 Global Reach Add/Set-AzExpressRouteCircuitConnection cmdlet changes. #10990
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If using RehydratePriority, then the source blob is already in archive. Destination blob cannot also be in archive with copyblob
[Storage] Show RequestId when StorageException don't have ExtendedErrorInformation, and fix a help example
[Compute] ColocationStatus for PPG.
DeploymentManager module update for new API version
…yptionSetId parameter to New-AzDiskUpdateConfig and New-AzSnapshotUpdateConfig
Update Set-AzNetworkWatcherConfigFlowLog.md
Make -Scope optional in *-AzPolicyAssignment cmdlets
[Compute] Disk encryption update
Retargeting master pull request to release branch
powershell cmdlets for connection monitor V2
Closed
8 tasks
amwate
changed the title
S164 Updating versions for Network and SQL Changes
Merge release branch -> master for 3.4.0
isra-fel
requested changes
Feb 3, 2020
...ExpressRouteCircuit/Peering/Connection/SetAzureExpressRouteCircuitConnectionConfigCommand.cs
Show resolved
Hide resolved
|
|
||
| if (null == circuitconnection) | ||
| { | ||
| throw new ArgumentException(string.Format("Circuit Connection with Name {0} was not added to the private peering", Name)); |
| using System.Management.Automation; | ||
|
|
||
| namespace Microsoft.Azure.Commands.Network { | ||
| [CmdletOutputBreakingChange(typeof(PSExpressRouteCircuit), DeprecatedOutputProperties = new[] { "AllowGlobalReach" })] |
Member
There was a problem hiding this comment.
Why will there be a breaking change?
Contributor
Author
|
Creating a new pull request #11501. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
38 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We are in the process of adding support for IPv6 in ExpressRouteCircuitConnectionConfig.
In the process, we have updated the existing PowerShell cmdlet
Add-AzExpressRouteCircuitConnectionConfig to accept another optional parameter AddressPrefixType (that optionally specifies the address family type for the address prefix).
In addition, we also introduced another cmdlet to modify the existing ExpressRouteCircuitConnectionConfig to add a new block IPv6CircuitConnectionConfig as well.
This would be used to update any existing GlobalReach configuration (ExpressRouteCircuitConnection) configurations.
Below is the design PR
https://github.com/Azure/azure-powershell-cmdlet-review-pr/issues/451#event-2913187208
This pull request brings in the changes in the powershell sdk.
The relevant swagger changes are to be merged in network-december-release.
Azure/azure-rest-api-specs#8145
NRP changes are already merged.
Checklist
CONTRIBUTING.mdChangeLog.mdfile(s) has been updated:ChangeLog.mdfile can be found atsrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md## Upcoming Releaseheader -- no new version header should be added