Closed almenscorner closed 6 months ago
Attention: Patch coverage is 99.72678%
with 3 lines
in your changes are missing coverage. Please review.
Project coverage is 97.55%. Comparing base (
b8b1341
) to head (fce0209
). Report is 6 commits behind head on main.
Files | Patch % | Lines |
---|---|---|
src/IntuneCD/intunecdlib/graph_request.py | 92.59% | 2 Missing :warning: |
...ntuneCD/update/Intune/update_compliancePolicies.py | 99.40% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
New Features
A new argument for retrieving audit data and creating commits based on the user UPN and action has been added. By just including
--audit
when running a backup, IntuneCD will check the Intune audit log for who made the change, set the UPN as the git user and commit the change in that users name. Additionally, if you want to get audit data further back than the default 24h, an env key can be set to the number of days you'd like to grab,AUDIT_DAYS_BACK
. Payloads that supports audit checks are:Example commit message:
Scope Tags is now backed up with the name instead of ID and compared using the name when updating minimising the risk of conflicts between tenants.
Backup, update and remove custom compliance scripts for Linux and Windows
Backup, update and remove compliance polices for Linux
Fixes
Other updates
Notes
Be aware that this update will cause commits in your repo as the scope tags on payloads will change from the ID to the name instead.
If you are planning to use
--audit
and do not want that the last user from the audit log is committing changed to documentation and other files not included in the audit run, make sure to configure your git user and email after IntuneCD has run the backup. Also remove--global
from thegit config
to make sure it's set locally for the repo.closes #178 closes #177 closes #180