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
but cannot add to SelectorsByObject directly (since I cannot create instances of internal.Selector):
selectors[&corev1.Service{}] =// can't instantiate object here
This results in a moderately strange workaround in my use case, where I want to include OpenShift Routes in SelectorsByObject only when my controller is running on OpenShift:
If the internal.Selector type is intended to be internal, then cache.SelectorsByObject should not use it. If it's intended to be used externally, it should not be in an internal package.
The text was updated successfully, but these errors were encountered:
If the internal.Selector type is intended to be internal, then cache.SelectorsByObject should not use it. If it's intended to be used externally, it should not be in an internal package.
I'm trying out the
SelectorsByObject
cache option introduced in v0.9.0, and noticed a bit of a strange setup. The type forSelectorsByObject
isThis results in
SelectorsByObject
values being semi-accessible, e.g. I can create objects with the internal typeSelector
in a map initialization:but cannot add to
SelectorsByObject
directly (since I cannot create instances ofinternal.Selector
):This results in a moderately strange workaround in my use case, where I want to include OpenShift Routes in
SelectorsByObject
only when my controller is running on OpenShift:If the
internal.Selector
type is intended to be internal, thencache.SelectorsByObject
should not use it. If it's intended to be used externally, it should not be in an internal package.The text was updated successfully, but these errors were encountered: