-
Story
-
Resolution: Done
-
Normal
-
ACM 2.15.0
-
None
-
Quality / Stability / Reliability
-
5
-
False
-
-
False
-
-
-
-
ACM Console Train 31 - 2
-
None
Value Statement
Ensure the issue title clearly reflects the value of this user story to the
intended persona. (Explain the "WHY")
Definition of Done for Engineering Story Owner (Checklist)
- Implement client-side caching using a global state management library (like Zustand)
- When multiple components are using the useFleetK8sWatchResource hook for the same query, a single watch is maintained and all callers receive live updates. (Currently, processing of the WebSocket only updates the state of the first hook called.)
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the Customer
Portal Doc template that you can access from [The Playbook](
and ensure doc acceptance criteria is met.
- Call out this sentence as it's own action:
- [ ] Link the development issue to the doc issue.
Support Readiness
- [ ] The must-gather script has been updated.