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
On applyconfigurations/meta/v1 I wonder why ManagedFieldsEntryApplyConfiguration is not nested on ObjectMetaApplyConfiguration.
Is this by design?
Asking because []ManagedFieldsEntry belong to .metadata .
The implementation of ManagedFieldsEntryApplyConfiguration would fit similarly what []OwnerReferenceApplyConfiguration and methods are currently performing on ObjectMetaApplyConfiguration.
Thanks,
Rafa
PS: Some may ask why I want to set ManagedFieldsEntry if K8s server side deals with this automatically. I want to build unit tests to parse a variation of ManagedFieldsEntry from a given object.
The text was updated successfully, but these errors were encountered:
Hi,
On
applyconfigurations/meta/v1
I wonder whyManagedFieldsEntryApplyConfiguration
is not nested onObjectMetaApplyConfiguration
.Is this by design?
Asking because
[]ManagedFieldsEntry
belong to.metadata
.The implementation of
ManagedFieldsEntryApplyConfiguration
would fit similarly what[]OwnerReferenceApplyConfiguration
and methods are currently performing onObjectMetaApplyConfiguration
.Thanks,
Rafa
PS: Some may ask why I want to set ManagedFieldsEntry if K8s server side deals with this automatically. I want to build unit tests to parse a variation of ManagedFieldsEntry from a given object.
The text was updated successfully, but these errors were encountered: