Offload user filtering to Azure API to avoid resource issues in large AD #227
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Suggested fix for #198 where we get failures testing for guest accounts in large AD because we run out of memory (after waiting a LONG time for the whole AD to be downloaded)
This PR could allow a wrapper profile (such as CIS Azure) to offload filtering to Azure instead of pulling all the accounts back to the Inspec machine to perform local filtering. This is especially useful in AD with more than 500k accounts.
This PR would allow the CIS Azure profile to test in a similar way to this:-