This repository has been archived by the owner on Jan 14, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
Production: Audit logs #10
Labels
Milestone
Comments
In next stages audit log can also catch events of started/stopped/killed/failed containers (can be handled by Harbor - not as part of RKD of course) |
Idea: An output of each task could be always logged in to files (file per task per execution time for example) when audit log is enabled |
blackandred
added a commit
that referenced
this issue
Jun 11, 2020
blackandred
added a commit
that referenced
this issue
Jun 11, 2020
Partially implemented for RKD 1.0, moving to RKD 1.1, cannot afford for so many tasks to release. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
The idea:
I think that on production it would be nice to have audit logs of all operations performed in RKD (when eg. RKD_AUDIT_LOG=true).
Why?
Proposed solution:
When
RKD_AUDIT_LOG=true
in.env
is present, then log every command to a log file eg..rkd/audit-log-2020-05-01.log
in a format, example:Potential issues:
Passwords leaking - user must be aware of the risk, documentation should inform about this
The text was updated successfully, but these errors were encountered: