Timeline for the release of 3.0.0

[mahendrapaipuri]

Hello,

Thanks for this awesome plugin. When can we expect the release of 3.0.0? We are interested in the #1072 where our use case relies on X-Grafana-User header.

Cheers!!

[yesoreyeram]

Hiya @mahendrapaipuri.. Sorry for the delay. Team is just getting back to full capacity after the holiday season. I added a tentative milestone in https://github.com/grafana/grafana-infinity-datasource/milestone/1 ( 14th feb 2025 ) to track this. But I guess it may be sooner than that given we are aiming to release these as beta before end of this month.

Also any feedback appreciated regarding #1072 ( you can test this yourself to see if this fits your use case )

[mahendrapaipuri]

Hello there @yesoreyeram Thanks a lot for the response. No worries, mid feb is perfect. Just wanted to plan our upgrades depending on the release timeline.

Well, I have already tested #1072 and it is perfect for our use case and it is working as intended. Thanks a lot for this!!

Do you think it is more appropriate that Grafana sends the config parameter send_user_header to plugins which they can expose it using the GrafanaCfg struct to backend plugins. This way we check for this config parameter and if it is true, we set the X-Grafana-User-Header in the requests to DS. This avoids configuring the "same" parameter twice: Grafana config and plugin config. Do you think that makes sense?

[yesoreyeram]

Leveraging grafana config perfectly makes sense for many cases and many other plugins. But for infinity, user may be using for different endpoints and different use cases where some of APIs require doesn't like additional headers or require different way of sending those values such as body, query string, different keys etc. so I am bit hesitant to leverage the generic key automatically and instead want the user take informative decision.

[yesoreyeram]

Let me know if any another aspect i missed