- Notifications
You must be signed in to change notification settings - Fork928
Closed
Milestone
Description
As we're quickly building/changing features, we need to ensure the audit log is capturing an accurate trail of user actions.
A 🦈 has caught a couple of issues, but we need to do a comprehensive list of CRUD actions (CLI and dashboard) and ensure they're being accurately represented.
- audit: Two entries created for adding a auto-stop time of 1 hour #4317
- audit: I deleted a workspace but the audit logs did not record it. #4316
The intended behavior is documentedhere.
Additionally, we should have a process in place for ensuring incoming features (#4125,#4311) are represented in the audit log. Can we do this via automated tests or should we build something into the product/QA process?
It's better to start thinking about this now before we introduce a lot of debt.
Metadata
Metadata
Assignees
Labels
No labels