feat(m365): add separate directory for adhoc scans#21
Merged
Conversation
…g files container now only reads from respective directory local config files are added to both directories
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
adhocandscheduleddirectories in the input storage container. Container instances will only run on configs in their respective directory.💭 Motivation and context
Provides a mechanism to run adhoc scans on a subset of tenants. Closes #7
🧪 Testing
Confirmed container instances read from specified directories. Tested running contain with no config files
✅ Pre-approval checklist
✅ Post-merge checklist