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
Currently Context.getSecondaryResource() returns only one optional resource. This is done from the cache of an event source. (Note that ideally there is only one event source for one type of resource.) But a reconciler could manage multiple resources of a same type. For example manage multiple Deployment for a custom resource.
So we should probably add Context.getSecondaryResources() (plural) that returns a list. See this handled in this PR: #1161
We should probably extend this to all event source, so from the mentioned PR to have all ResourceEventSource implement MultiResouceOwners. Since this is generally a something can occur with any resources.
For dependent resource, since one dependent resource always represents one resource not multiple, there would be a discriminator mechanism to distinguish to which resource it belongs to among related resources.
The text was updated successfully, but these errors were encountered:
Currently
Context.getSecondaryResource()
returns only one optional resource. This is done from the cache of an event source. (Note that ideally there is only one event source for one type of resource.) But a reconciler could manage multiple resources of a same type. For example manage multipleDeployment
for a custom resource.So we should probably add
Context.getSecondaryResources()
(plural) that returns a list. See this handled in this PR:#1161
We should probably extend this to all event source, so from the mentioned PR to have all
ResourceEventSource
implementMultiResouceOwners
. Since this is generally a something can occur with any resources.For dependent resource, since one dependent resource always represents one resource not multiple, there would be a discriminator mechanism to distinguish to which resource it belongs to among related resources.
The text was updated successfully, but these errors were encountered: