Fix bookmark event handling in watch operations #116
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.
Summary
Fix handling of Kubernetes BOOKMARK events in watch operations to prevent validation errors when watching resources.
Problem
BOOKMARK events in Kubernetes watch streams contain minimal object data - only
metadata.resourceVersion
field is included. When cloudcoil tried to validate these minimal objects against the full resource schema, it would fail for resources with non-nullable fields, causing watch operations to crash.Solution
BookmarkEvent
fromWatchEvent
to handle them differentlyUnstructured
objects to avoid validation errorswait_for
operationsChanges
BookmarkEvent
type separate fromWatchEvent
Unstructured
andBookmarkEvent
types in API clientwait_for
operations with proper type assertionsTesting
This fix resolves the validation crashes reported in issue #115 when bookmark events are received during watch operations.
Fixes #115