Track dependency objects even if they don't exist #1082
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should fix #1028.
In order to be able to track objects that don't exist yet,
tracker.Tracker
tracks objects by areconciler.Key
consisting of itsschema.GroupKind
and itstypes.NamespacedName
.Given the
schema.GroupKind
is derived from the objectTypeMeta
, I made sure that every object instantiated in tests has it set. I believe this should also be the case in production.In order to make sure the
schema.GroupKind
was properly taken into account, I modified thetesthelpers.FakeTracker
to use the fullreconciler.Key
as its tracking key.I wasn't able to run the end-to-end tests locally, unfortunately. Unit tests are passing but it would be nice if someone on the team could check the end-to-ends are also happy.
Please take a look and let me know how it looks!