You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 16, 2024. It is now read-only.
Requests to list and watch events should never strip event details.
Background
The details field of a runtime event allows for context specific information to be added. For example, VCS info is included for AppImagePull events.
By default, the runtime API elides the field on list and watch unless otherwise opted-in by the request. The idea was to reduce the overhead when working with lots events containing potentially large details.
Motivation
This was likely a premature optimization since, in practice, the details field has been used to store small payloads, similar in size to their respective objects.
The text was updated successfully, but these errors were encountered:
Description
Requests to list and watch events should never strip event details.
Background
The details field of a runtime event allows for context specific information to be added. For example, VCS info is included for AppImagePull events.
By default, the runtime API elides the field on list and watch unless otherwise opted-in by the request. The idea was to reduce the overhead when working with lots events containing potentially large
details
.Motivation
This was likely a premature optimization since, in practice, the details field has been used to store small payloads, similar in size to their respective objects.
The text was updated successfully, but these errors were encountered: