Skip to content

Keep rotating log of valid commands that aren't authorized #13

@linucksrox

Description

@linucksrox

So we should check the commands first before checking the authorization, after all. I kept going back and forth in my mind about which way was better, but it really didn't matter before this idea came up.

If a command comes in that is tied to any enabled actions, but then the user is not authorized, we can keep a log of that somewhere which will help greatly with troubleshooting. This should be optional because not everybody needs logging, and disabled by default to minimize storage usage and computations (apparently).

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions