• Dmitry Shulyak's avatar
    Fix FakeNodeHandler Update behaviour · 0ddaa20b
    Dmitry Shulyak authored
    Two problems:
    1. Get is always using Existing nodes slice, and you will for sure miss any
       updated data
    2. Each Update duplicates node entry in UpdatedNodes slice
    
    For the 1st, try to find a node in UpdatedNodes slice (same as for the List).
    2nd - append only if there is no node with same name as updated, if there is
    just replace object.
    
    Change-Id: I9ef1cca2788ba946eee37fa1b037c124ad76074c
    0ddaa20b
Name
Last commit
Last update
..
certificates Loading commit data...
daemon Loading commit data...
deployment Loading commit data...
disruption Loading commit data...
endpoint Loading commit data...
framework Loading commit data...
garbagecollector Loading commit data...
job Loading commit data...
namespace Loading commit data...
node Loading commit data...
petset Loading commit data...
podautoscaler Loading commit data...
podgc Loading commit data...
replicaset Loading commit data...
replication Loading commit data...
resourcequota Loading commit data...
route Loading commit data...
scheduledjob Loading commit data...
service Loading commit data...
serviceaccount Loading commit data...
volume Loading commit data...
OWNERS Loading commit data...
controller_ref_manager.go Loading commit data...
controller_utils.go Loading commit data...
controller_utils_test.go Loading commit data...
doc.go Loading commit data...
lookup_cache.go Loading commit data...