-
Notifications
You must be signed in to change notification settings - Fork 1.2k
⚠️ Fakeclient: Fix a number of bugs when updating through apply #3319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
7aee523
to
e5e79f5
Compare
8e536d1
to
a8c73d7
Compare
a8c73d7
to
535ae6b
Compare
Thank you very much! /lgtm |
LGTM label has been added. Git tree hash: 52f5bd390f08a0938a3e8958ab16b46c962b664e
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alvaroaleman, sbueringer The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Prior to this, updates through Apply did not call
versionedTracker.updateObject
which does a number of things such as:The reason this happend is that
versionedTracker
embedded antesting.ObjectTracker
and as a result, we inherited theApply
of that upstream tracker rather than implementing our own.This PR contains three commits:
versionedTracker
into its own fileversionedTracker
atesting.ObjectTracker
and stop embedding its upstreamupdateObject
from the versioned trackersApply
and update things as needed, as well as adding tests/assign @sbueringer
/hold