Skip to content

PerResourcePollingEventSource should only fetch resource on demand on first call #1168

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
csviri opened this issue Apr 21, 2022 · 0 comments · Fixed by #1169
Closed

PerResourcePollingEventSource should only fetch resource on demand on first call #1168

csviri opened this issue Apr 21, 2022 · 0 comments · Fixed by #1169
Assignees
@csviri
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@csviri
Copy link
Collaborator

csviri commented Apr 21, 2022

Currently if the resource is not found in the cache is always fetched from the supplier. This should be done only once, from that point the resource should be read only from cache.

Note that this event source does not do syncing on startup. So reading the resource from it first time basically the "syncing".
@csviri csviri added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 21, 2022
@csviri csviri self-assigned this Apr 21, 2022
@csviri csviri linked a pull request Apr 21, 2022 that will close this issue
All Resource Event Sources can handle multiple seconday resources for a primary resources #1169
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@csviri csviri

Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
1 participant
@csviri