audit: log update workspace events #4624
Assignees
Comments
|
contigent on #4625 |
|
This issue is becoming stale. In order to keep the tracker readable and actionable, I'm going close to this issue in 7 days if there isn't more activity. |
This was referenced Jan 3, 2023
|
@bpmct A potentially easy way to do this would be to include the template version ID in the diff of the workspace build audit log line (imagine the below line item with a diff showing old and new template version ID): Would this be sufficient or do we need a distinct line item like "Admin started workspace build for foo with template version bar"? |
|
The version ID in the diff is definitely a good start! We can just scope it to that for now |
|
Resolved by #5841 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If a template changes, the user may update an associated workspace, either in the CLI (
coder update "workspace-1"), or in the UI:Additionally, in the future, we might make it possible for users to toggle between template versions in the UI.
We should audit these template version changes. One easy way might be to include the
template_version_idin the workspace build diff, but we should check that 1) this works when we're updating via the CLI and 2) that this satisfies the product requirement, as we won't have a separate line item for workspace template changes.The text was updated successfully, but these errors were encountered: