Run Obligatron daily at 7AM #1078
Merged
Conversation
This file contains 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
|
This is a cron method. Did we consider an event driven method, running the lambda once the task to collect the |
AshCorr
force-pushed
the
ash/obligatron-schedule
branch
from
1ff8c2c to
bc6ece1
Compare
I think that would be ideal, for the sake of building a base line lets do it daily for now though till we figure out how to link the Cloudquery jobs to this Lambda! |
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.
What does this change?
Run Obligatron daily at 7AM
Why?
So that we can start building a historical view and get an understanding of how much data there is (once we enable Security Hub on all accounts that is!)
How has it been verified?
Ran snapshot test.