Skip to content
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

Add Native Support for API Endpoints as Datasource with Inifnity Plugin #788

Closed
pruthvi6767 opened this issue Jul 13, 2022 · 1 comment
Closed
Labels
enhancement New feature or request triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@pruthvi6767
Copy link

pruthvi6767 commented Jul 13, 2022

Is your feature request related to a problem? Please describe.
I have a usecase where I use a REST API Result Set as my Datasource to visualize metrics. I am using the infinity plugin to create the Datasource with Oauth2 Client Credentials. I see Grafana currently supports Times Series Datastores natively. Please consider this usecase
I have deployed Grafana using the grafana-operator and the Datasource type fields do not currently support the "Oauth Type" field or plugin directly.
Types defined in Plugin Code https://github.com/yesoreyeram/grafana-infinity-datasource/blob/main/pkg/infinity/settings.go#L32-L42

Describe the solution you'd like
I would like to see the types "oauth2", "clientCredentials", supported in the Datasource types (in jsonData) support for the Infinity plugin

@pruthvi6767 pruthvi6767 added enhancement New feature or request needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 13, 2022
@pruthvi6767 pruthvi6767 changed the title Add type fields for DataSource with Inifnity Plugin Add Native Support for API Endpoints as Datasource with Inifnity Plugin Jul 20, 2022
@pb82
Copy link
Collaborator

pb82 commented Jul 26, 2022

this will be fixed with #803

@NissesSenap NissesSenap added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 26, 2022
@pb82 pb82 closed this as completed Aug 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants