v2.2.1

Issues

• Fix policydefinition and policysetdefinition removal of 'empty' conditional logic (#810)

Dependencies

• Increment required module versions (#811)
  • PSFramework (1.8.289)

v2.2.0

Issues

• Fix Deletion Delimiter Logic (#792)

Enhancements

• Adding support for custom Jq templates (#789)

Dependencies

• Increment required module versions (#804)
  • Az.Accounts (2.12.3)
  • Az.Billing (2.0.2)
  • Az.Resources (6.7.0)

v2.1.2

Issues

🚒 Push failing, the property definitionVersion is exported for policySetDefinitions when using the graph that was introduced in 2.0.0.

• Remove property definitionVersion from policySetDefinitions (#781 )

v2.1.1

Issues

🚒 Push failing, affecting deployment of objects at and below Subscription scope. The issue affects deployments running v2.0.0 and later when there is “No management group”.

• Fix regression of Subscription Only Discovery with no Management Group (#778)

v2.1.0

Thank you @borondy for your contributions to this release!

Issues

• Fix regression of #538 (#773)

Enhancements

• Adding Removal of Lingering Files (#764)
• Throw exception on failing bicep build (#768)

Dependencies

• Increment required module versions (#769)
  • Az.Accounts (2.12.1)
  • Az.Resources (6.5.3)

v2.0.2

Issues

• Updated default ThrottleLimit to mitigate #757 as well as address considerations described in https://github.com/azure/azops/wiki/performance-considerations
• Updated logic for (#700) to also handle square brackets [ ]. Closing #755

Enhancements

• Added retry logic for policyExemptions, roleDefinitions/Assignments as well as locks

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:

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
   

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

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

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)