Releases: Azure/AzOps
v2.0.1
Issues
🚒 Nested resource apiVersion returned by Az.ResourceGraph
, specifically deployIfNotExists
policies containing unwanted information.
- Patch apiVersion on nested microsoft.authorization/policydefinitions resources (#751)
🔗 For more information on AzOps 2.0.0
v2.0.0
Overview
With a wide array of pivotal changes in the codebase, this represents a major leap forward for AzOps reaching version 2.0.0 🎉
Key goals:
-
Significantly improve overall
Pull
performance.
See below screenshot for comparison between1.9.4
and2.0.0
in an environment with 1000+ subscriptions
-
Support Pull and Push of
zones
information.
Breaking Changes ❌
Description:
From this version, the logic for determining which resource groups to include has been updated to only consider SubscriptionIDs specified in the Core.SubscriptionsToIncludeResourceGroups
setting. In previous versions, the logic also took into account DisplayNames specified in this setting. As a result, users may notice changes in which resource groups are pulled back if currently filtering using DisplayName.
Reason:
The filter is intended to be deterministic, since display names can be duplicated, we have removed that part of the logic.
Significant changes ⚠️
- Please be advised that due to the change to
Az.ResourceGraph
, the data model has slightly changed. As a consequence, the first pull that runs on version 2.0.0 will generate a larger pull request than usual.
For that reason, if you are using the AzOps resource deletion feature for autogeneratedpolicyAssignments
,policyDefinitions
,policySetDefinitions
,policyExemptions
,roleDefinitions
androleAssignments
, it requires you to run an Pull on version 2.0 before initiating deletion. If not, you will receive the following error
Deletion is currently only supported for policyAssignments, policyDefinitions, policyExemptions, policySetDefinitions and roleAssignments. Will NOT proceed with deletion of file root/....
-
Also note that we have reduced the verbosity of some output in the module to optimize performance. If you want additional debug output, change the
Message.Info.Maximum
setting in settings.json to a higher level (up to 9) -
Autogenerated templates for
roleAssignments
will no longer include displayName for the assigned principal due to API changes.
Issues
- Public Ip; zones are removed on AzOpsPull command (#701)
Enhancements
v1.9.4
v1.9.3
Issues
Enhancements
Dependencies
v1.9.2
Thank you @bjompen and @jsandquist for your contributions to this release!
Issues
- Update Management Group DisplayName (#724)
Enhancements
- Add support for wildcard in setting Azops.Core.IncludeResourcesInResourceGroup (#713)
- Expand support for management group deployment (#718)
- Fix headlines for WhatIf output (#719)
- Remove Directory Readers Azure AD role requirement for roleAssignments pull (#723)
Dependencies
- Increment required module versions (#720)
- Az.Resources (6.4.1)
v1.9.1
Enhancements
- Add invalid characters logic (#700)
Note: This feature introduces a behaviour that remove invalid characters at filename creation. This harmonizes filename characters to ensure illegal filesystem characters are replaced/not part of filenames generated. - Added graceful error handling for child resource export (#705)
Features
- Add Microsoft.authorization/locks support (#704)
Note: This feature is configurable through a new setting Core.SkipLock in settings.json. Have a look at Azure/AzOps-Accelerator#127 for further details.
Dependencies
- Increment required module versions (#698)
- Az.Accounts (2.10.3)
- Az.Resources (6.4.0)
- PSFramework (1.7.249)
v1.9.0
Features
- Adding Deletion Support for Resource Types policyDefinitions and policySetDefinition (#687)
Note: For GitHub Actions, this feature require a minor update in the Validate pipeline. Read https://github.com/azure/azops/wiki/ResourceDeletion#deletion-dependency-validation for further details.
Dependencies
v1.8.3
v1.8.2
Thank you @SimonWahlin and @egullbrandsson for your contributions to this release!
Issues
- Improved error handling coming from failing resource providers (#651, #644)
- Subscription not being placed under the correct management group folder (#654, #655)
- Fix verbose log message for bicep templates (#658, #659)
- Comments cannot be longer than 150000 characters (#652, #665)
Dependencies
- Increment required module versions (#650)
- PSFramework (1.7.237)
v1.8.1
Thank you @CerveloRS for reporting the issue swiftly!
Issues
🚒 Undocumented breaking change discovered in Az.Resources 6.0.0
- Fix issue in Get-AzManagementGroups causing partial discovery to fail "Management Group not found" (#640)