feat: add VM overview status#13232
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
π‘ Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ee546405c3
βΉοΈ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with π.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "formatZH": "εζ₯θζζΊη½η»", | ||
| "formatEN": "sync VM networks" | ||
| }, | ||
| "/core/enterprise/vms/networks/update": { |
There was a problem hiding this comment.
When /api/v2/core/enterprise/vms/networks/sync is called, OperationLog only creates an operation record if record.Path is present in docs.XLogJson; after removing this entry, the middleware falls through at the !hasPath check and the VM network sync action is no longer audited, unlike the adjacent VM network create/update/delete operations.
Useful? React with πΒ / π.
| "formatZH": "εζ₯θζζΊεε¨", | ||
| "formatEN": "sync VM storages" | ||
| }, | ||
| "/core/enterprise/vms/storages/update": { |
There was a problem hiding this comment.
The same audit-log lookup also depends on this JSON entry for /api/v2/core/enterprise/vms/storages/sync; deleting it means successful storage-pool sync requests skip operation-log creation entirely, while the neighboring storage create/update/delete endpoints continue to be logged.
Useful? React with πΒ / π.
1 participant
No description provided.