The useEffects on the useSetupTechnology hook is causing multiple updates for the setupTechnology hook in Fleet. Weshould also look at the other useEffects because there seems to be many renders for Agentless flow
It can be potentially improved by converting useEffects with imperative code into a more declarative approach (useCallback, useMemo), this ticket aims to improve readability and maintainability by removing the useEffects.
Definition of done
[ ] useEffects removed from useSetupTechnology hook
[ ] All the tests still pass and no functionality is loss
[ ] It should account for all the scenarios when toggling between agentless and agent-based.
Motivation
The useEffects on the useSetupTechnology hook is causing multiple updates for the setupTechnology hook in Fleet. Weshould also look at the other useEffects because there seems to be many renders for Agentless flow
It can be potentially improved by converting
useEffects
with imperative code into a more declarative approach (useCallback, useMemo), this ticket aims to improve readability and maintainability by removing theuseEffects
.Definition of done
useEffects
removed from useSetupTechnology hookOut of scope
Related tasks/epics