Skip to content

Commit daa2d32

Browse files
isra-felNoriZC
andauthored
Update release notes of Az.Subscription 0.11.0 (#23358)
* Update release notes of Az.Subscription 0.11.0 * Update src/Subscription/ChangeLog.md Co-authored-by: NoriZC <[email protected]> --------- Co-authored-by: NoriZC <[email protected]>
1 parent fff68ea commit daa2d32

File tree

1 file changed

+18
-10
lines changed

1 file changed

+18
-10
lines changed

src/Subscription/ChangeLog.md

Lines changed: 18 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -20,16 +20,24 @@
2020
## Upcoming Release
2121

2222
## Version 0.11.0
23-
* Invoke-AzSubscriptionAcceptOwnership:
24-
- Added alias `-DisplayName` to parameter `-SubscriptionName`.
25-
* New-AzSubscriptionAlias:
26-
- Added alias `-DisplayName` to parameter `-SubscriptionName`.
27-
* Rename-AzSubscription:
28-
- Changed parameter `-SubscriptionName` to required.
29-
- Added alias `-DisplayName` to parameter `-SubscriptionName`.
30-
* Removed cmdlet `Update-AzSubscriptionPolicy`
31-
* Get-AzSubscriptionAcceptOwnershipStatus
32-
- Updated parameter type of `SubscriptionId` from `string[]` to `string`.
23+
24+
### Issue summary
25+
26+
When the PowerShell module Version 0.10.0 of the Az.Subscription got released, it was reported that there were significant number of breaking changes related to mismatch of parameters that got added to the module. Our public facing help document also depicted the older version of the module and hence there was a discrepancy.
27+
28+
#### Why did this happen?
29+
30+
The latest module that got auto generated from Swagger resulted not only in changing certain parameter names, but also introducing new parameters which we did not support in the past. Additionally, our public help facing document was still displaying the module with older cmdlet parameters that was a cause of confusion.
31+
32+
#### How did we remedy?
33+
34+
We did a hotfix for this issue and created a new release 0.10.2. Most of the changes made, reflect parity with the public Swagger and we have now fixed the parameters issue. Features of the new release mentioned below:
35+
36+
1. `New-AzSubscriptionAlias` now supports additional input "ManagementGroup" to associate the subscription with, additional owner and tenant for the subscription.
37+
1. The parameter `SubscriptionName` has been changed to `DisplayName`. However, `SubscriptionName` is still available as an alias parameter for `DisplayName`.
38+
1. `Updated-AzSubscription` cmdlet which was used for cancel, enable, and rename operations is replaced with new separate cmdlets to directly reflect actions: `Disable-AzSubscription`, `Enable-AzSubscription`, and `Rename-AzSubscription`.
39+
1. New cmdlets (`Get-AzSubscriptionAcceptOwnershipStatus` & `Invoke-AzSubscriptionAcceptOwnership`) are introduced to handle / to work with invitation model - to get the status and to accept the invitation for new subscription creation.
40+
1. Public documentation updated for PowerShell version for create subscription flow as 0.9.0.
3341

3442
## Version 0.10.1
3543
* Removed the default value for the `New-AzSubscriptionAlias` cmdlet parameter `SubscriptionId`.

0 commit comments

Comments
 (0)