Releases: gettek/terraform-azurerm-policy-as-code
Releases · gettek/terraform-azurerm-policy-as-code
2.9.2
2.9.1
2.9.0
What's Changed
ENHANCEMENTS:
- Most requested: Re-using the same policy definition multiple times in an initiative (#97 / #67 / #40 / #37)
- see the
initiative
README
- see the
- Lifecycle replacement triggers for Policy Set Definition member updates (#94 / #50 / #36)
- adding/removing definitions from a set or updating definition parameters would often cause the resource manager API to complain
- Note: this may introduce a breaking change to existing builds in which case redeployment of sets and set_assignments will be required
- requires terraform >= 1.4
FEATURES:
- Dynamically build initiative non-compliance messages based off values present in the definition, in order of:
metadata.non_compliance_message
,description
,display_name
- Default message:
Flagged by Policy: <policy_name>
UPDATES:
- 2.9.0 by @gettek in #100
- Full Changelog: 2.8.3...2.9.0
2.8.3
What's Changed
- Fixes Definition metadata and parameter validation (#90 & #91)
- Update list of supported Resource Provider Modes
- 2.8.3 by @gettek in #92
Full Changelog: 2.8.2...2.8.3
2.8.2
2.8.1
What's Changed
- fix definition object properties by @thecomalley in #80
- 2.8.1 by @gettek in #81
Full Changelog: 2.8.0...2.8.1
2.8.0
What's Changed
*_assignment
modules in #73:- Breaking Change:
re_evaluate_compliance [bool]
replacesresource_discovery_mode [string]
- setting this to
true
will Re-Evaluate Compliance for remediation tasks
- setting this to
- New Feature: support for Resource selectors (preview) and Overrides (preview) - requires
AzureRM >=3.49.0
- Fix output for
definition_reference_ids
and added outputinitiative.reference_ids
- Prevent remediation when
assignment_enforcement_mode=false
by @pmatthews05 in #72
- Breaking Change:
- Bumped minimum provider version requirements
- Improved pre-commit
- Fixes #68
- Fixes #71
New Contributors
- @pmatthews05 made their first contribution in #72
Full Changelog: 2.7.2...2.8.0