Breaking Changes
Script Export-AzPolicyResources replaces Build-PolicyDefinitionFolder with a substantial increase in capability. It has a round-trip capability supporting the extract to be used in the build Definitions.
Introducing a new approach using PowerShell Module. This not (actually) breaking existing implementation since you can continue as is; however, for a simplified usage of EPAC, the PowerShell module is the best approach.
The move from synchronizing your repo with the GitHub repo to a PowerShell module necessitated the reworking of the default values for Definitions, Output, and Input folders. Many scripts use parameters for definitions, input and output folders. They default to the current directory, which should be the root of the repo. make sure that the current directory is the root of your repo. We recommend that you do one of the following approaches instead of accepting the default:
Set the environment variables PAC_DEFINITIONS_FOLDER, PAC_OUTPUT_FOLDER, and PAC_INPUT_FOLDER.
Use the script parameters -definitionsRootFolder, -outputFolder, and -inputFolder (They vary by script).
Added support for GitHub Actions in the StarterKit folder.
What's Changed
- Update CAF policy assignment by @anwather in #170
- Added cloud parameter to sync script by @anwather in #172
- Update 7.0 docs by @anwather in #174
- Update mkdocs.yml by @anwather in #175
- Document cleanup and script fixes by @techlake in #176
- Updated hardcoded value to reflect environment variable by @gjonn in #177
- Update EnterprisePolicyAsCode.psd1 by @anwather in #178
New Contributors
Full Changelog: 6.3.4...v7.0.0