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

chore(deps): Bump @grafana from 8 to 9 #197

Closed
wants to merge 1 commit into from
Closed

chore(deps): Bump @grafana from 8 to 9 #197

wants to merge 1 commit into from

Conversation

mmorel-35
Copy link
Contributor

@mmorel-35 mmorel-35 commented Nov 19, 2022

Starting from 9.0 version, Grafana deprecates the use of Data source proxy calls by id in favor of Data source proxy calls
see https://grafana.com/docs/grafana/latest/developers/http_api/data_source/#data-source-proxy-calls-by-id

This changes the actual configuration of the kumahq-kuma-datasource, the property to use is now prometheusDataSourceUid instead of prometheusDataSourceId.

Thi also upgrades the @grafana dependencies to use 9.4.3 versions

Concerning the handleErrors function, I found it in https://github.com/grafana/grafana/tree/main/public/app/plugins/datasource/prometheus

Signed-off-by: Matthieu MOREL [email protected]

@mmorel-35 mmorel-35 marked this pull request as ready for review November 20, 2022 11:15
@mmorel-35 mmorel-35 changed the title chore(deps): Use 9.0.X grafana API chore(deps): Use 9.X grafana API Nov 20, 2022
@mmorel-35
Copy link
Contributor Author

Hi @lahabana ,

I tried to use https://www.npmjs.com/package/@grafana/create-plugin , it seems nice but add way too many files compared to what I was trying to do. Maybe you'll find it interesting ?

@lahabana
Copy link
Contributor

Tried this create-plugin when started building this. It was way too limited for what we were doing and ended up not using it

Copy link
Contributor

@slonka slonka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but maybe @kleinfreund or @johncowen could weight in.

@kleinfreund
Copy link

LGTM but maybe @kleinfreund or @johncowen could weight in.

I had a look and don't see anything out of the ordinary, though actually assessing this functionality would require project familiarity and usage knowledge that I don't have.

@mmorel-35 mmorel-35 changed the title chore(deps): Use 9.X grafana API chore(deps): Use 9.3.X grafana API Feb 10, 2023
@mmorel-35 mmorel-35 changed the title chore(deps): Use 9.3.X grafana API chore(deps): Bump @grafana from 8 to 9.3.6 Feb 10, 2023
@mmorel-35
Copy link
Contributor Author

Any updates on this ?

@lahabana
Copy link
Contributor

@mmorel-35 need to find time to double check the compatibility

@mmorel-35 mmorel-35 changed the title chore(deps): Bump @grafana from 8 to 9.3.6 chore(deps): Bump @grafana from 8 to 9.4.3 Mar 3, 2023
@mmorel-35
Copy link
Contributor Author

Any chance it might be addressed soon ?
@Automaat, maybe ?

@mmorel-35 mmorel-35 requested a review from a team as a code owner October 22, 2023 19:05
@mmorel-35 mmorel-35 requested review from lobkovilya and lukidzi and removed request for a team October 22, 2023 19:05
@mmorel-35 mmorel-35 changed the title chore(deps): Bump @grafana from 8 to 9.4.3 chore(deps): Bump @grafana from 8 to 9 Oct 24, 2023
@mmorel-35 mmorel-35 closed this by deleting the head repository Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants