Issues
- Improvements for API eventsNAS-132666Caleb
- API events for `virtualization.instance.query`NAS-132582Resolved issue: NAS-132582William Gryzbowski
- Request Support New Authentication MethodNAS-131593Resolved issue: NAS-131593Triage Team
- Add Block I/O chart to app widgetsNAS-131217Resolved issue: NAS-131217Denys Butenko
- Not able to set password at first login (fresh install)NAS-130849Resolved issue: NAS-130849Triage Team
- App version vs Version is confusingNAS-130834Resolved issue: NAS-130834Alex Karpov
- in Discover applications, Icons disappear when searching resultsNAS-130636Resolved issue: NAS-130636Rehan Yousaf
- attempting to install an app fails without errorNAS-130635Resolved issue: NAS-130635Waqar Ahmed
- unable to refresh catalogNAS-130633Resolved issue: NAS-130633Waqar Ahmed
- Attempting to install MiniIO failsNAS-130632Resolved issue: NAS-130632TrueNAS Backend Triage
- Available Apps list should be in alphabetical orderNAS-130630Resolved issue: NAS-130630Denys Butenko
- Add "Reset" to configure dashboardNAS-130629Resolved issue: NAS-130629Denys Butenko
1-12 of 12
1 of 12
Improvements for API events
Description
Problem/Justification
None
Impact
None
Attachments
1
created by
is duplicated by
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Caleb
CalebReporter
Denys Butenko
Denys ButenkoLabels
Components
Affects versions
Priority

More fields
More fields
Katalon Platform
Katalon Platform
Created November 21, 2024 at 8:37 AM
Updated January 27, 2025 at 3:44 PM
Activity
Show:
Caleb November 21, 2024 at 4:34 PM
@Denys Butenko
we already send the response as the return from the crud methods, so just please use those returned objects in the meantime
we should probably consider adding events globally to middleware, however, this will have to be properly designed and implemented because it could potentially become very expensive.
William Gryzbowski November 21, 2024 at 12:32 PM
@Denys Butenko what existing code? Can you give examples of endpoints where it will return fields?
These changes would allow us to reuse existing code and remove a workaround to manage the collection state.
Example of websocket messages:
Actual result:
When creating a new instance:
added
event missingfields
propertyWhen start/stop/restart existing instance:
changed
event missing other instance fields exceptstatus
Expected result:
When creating a new instance:
added
event havefields
property with instanceWhen start/stop/restart existing instance:
changed
event have full instance fieldsNOTE: This is not a limitation of
virt.*
namespace. We just haven’t had sending events on crud events be global by design. It has always been an explicit feature that was added by the developer during the implementation of a plugin. We should consider sending events on CRUD events by default for all namespaces but that will have to come after we get the strictly versioned API feature complete. Also, adding this functionality will require careful consideration and design.