-
Notifications
You must be signed in to change notification settings - Fork 100
[FEATURE] add remote loader for runtime plugins #2514
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.
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
[FEATURE] add remote loader for runtime plugins #2514
Conversation
801ebe1
to
c3a89e8
Compare
looks like the e2e tests are broken but I suppose it's because it requires the new datasource plugin |
c3a89e8
to
4f79b3b
Compare
Signed-off-by: Gabriel Bernal <gbernal@redhat.com>
4f79b3b
to
bf9d406
Compare
I adjusted the plugin module structure to match better our types conventions as discussed. I added the changes from the plugins side here: perses/plugins#18 |
9a1223a
to
3ac835d
Compare
Signed-off-by: Gabriel Bernal <gbernal@redhat.com>
3ac835d
to
6e0ea0d
Compare
@jgbernalp PR looks good to me. I guess the failure of the e2e tests is due to the loading of the Prometheus datasource right ? I mean since the datasource plugin is not present yet (because it's not published) then the e2e tests cannot work |
yes exactly. I'll merge it then. Thnx for checking. |
Description
This PR uses the remote plugin loader to load all types of plugins at runtime, based on the installed plugins fetched from
api/v1/plugins
This will work in conjunction with perses/plugins#16 and perses/plugins#18