-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto event log generation when operation finishes #2088
Conversation
4bdd612
to
b3ce2ff
Compare
Codecov Report
@@ Coverage Diff @@
## master #2088 +/- ##
==========================================
+ Coverage 65.60% 65.68% +0.07%
==========================================
Files 65 65
Lines 4876 4890 +14
==========================================
+ Hits 3199 3212 +13
- Misses 1677 1678 +1
Continue to review full report at Codecov.
|
df52099
to
b3ce2ff
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks pretty good, just one suggestion for clarity
b3ce2ff
to
ec13291
Compare
7a58ee3
to
93f897f
Compare
when comments are resolved, please send to @bworrell for review |
Adding test for auto event log generation and changing method name Test style fix Clearer variable name
93f897f
to
e968821
Compare
Description
Event logs are automatically generated and written to disk when an operation finishes. The event log directory is placed in the
event_logs
subdirectory of thereports_dir
directory as specified in the CALDERA configuration (e.g./tmp/event_logs
). The event log file is of the formatoperation_$ID.json
, where$ID
is the operation's ID number.Type of change
How Has This Been Tested?
Added a test to verify the operation method to generate the event log file.
Checklist: