-
Notifications
You must be signed in to change notification settings - Fork 2.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
When executing the data-fingerprint command a log entry is written to… #30251
Conversation
… allow analysis who executed the command and when - refs #30154
Codecov Report
@@ Coverage Diff @@
## master #30251 +/- ##
============================================
+ Coverage 58.35% 58.37% +0.01%
- Complexity 18571 18574 +3
============================================
Files 1093 1093
Lines 63780 63796 +16
============================================
+ Hits 37221 37238 +17
+ Misses 26559 26558 -1
Continue to review full report at Codecov.
|
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.
👍
backport - yes/no ..... |
if safe, yes... |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
… allow analysis who executed the command and when
Description
Executing the data fingerprint command has some large impact on the system.
The command should be logged for later analysis who executed the command.
In addition it is worth a second user confirmation before applying the data-fingerprint.
Related Issue
refs #30154
Motivation and Context
Make owncloud a bit more robust
How Has This Been Tested?
Types of changes
Checklist: