Skip to content

Releases: Azure/AzOps

v2.0.1

17 Feb 17:48
c173b1f
Compare
Choose a tag to compare

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

17 Feb 11:54
0044809
Compare
Choose a tag to compare

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:

  1. Significantly improve overall Pull performance.
    See below screenshot for comparison between 1.9.4 and 2.0.0 in an environment with 1000+ subscriptions
    AzOps-2 0-baseline

  2. 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 autogenerated policyAssignments, policyDefinitions, policySetDefinitions, policyExemptions, roleDefinitions and roleAssignments, 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 

  • AzOps - Discovery Performance Issues (#438)
  • Updating Settings.json and Pull pipeline fails (#699)
  • Pull pipeline removing the metadata from policy exemptions and assignment file (#742)

v1.9.4

07 Feb 17:51
52678aa
Compare
Choose a tag to compare

Dependencies

  • Increment required module versions (#744)
    • PSFramework (1.7.270)
    • Az.Accounts (2.11.2) - fixes #737 🎉
    • Az.Resources (6.5.2)

v1.9.3

22 Dec 06:55
ba2d530
Compare
Choose a tag to compare

Issues

  • Fix WhatIf issue in #718 (#729)
  • Bicep deployment fix for parameter file updates (#733)

Enhancements

  • Undesired warning in pipeline output for parameter files during deployment/validate #717 (#733)

Dependencies

  • Increment required module versions (#728,#731)
    • Az.Accounts (2.10.4)
    • Az.Resources (6.5.1)

v1.9.2

07 Dec 14:43
a95af83
Compare
Choose a tag to compare

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

17 Nov 09:20
78d8f76
Compare
Choose a tag to compare

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

17 Oct 10:43
b94103f
Compare
Choose a tag to compare

Features

Dependencies

  • Increment required module versions (#689)
    • Az.Accounts (2.10.2)
    • Az.Resources (6.3.0)
    • PSFramework (1.7.246)
  • Add new required module (#687)
    • Az.ResourceGraph (0.13.0)

v1.8.3

21 Sep 19:34
dedc6a8
Compare
Choose a tag to compare

Issues

  • Ensure management group name uniqueness (#682)
  • Generalize Temp Pathing (#679)

Enhancements

  • Improved jq sort order (#669)

Dependencies

  • Increment required module versions (#682, #676)
    • Az.Accounts (2.9.1)
    • Az.Resources (6.1.0)
    • PSFramework (1.7.244)

v1.8.2

01 Jul 10:50
7ff5b7a
Compare
Choose a tag to compare

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

24 May 19:08
b6522ad
Compare
Choose a tag to compare

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)