-
Notifications
You must be signed in to change notification settings - Fork 11.8k
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
Pyroscope: Rename phlare to grafana-pyroscope-datasource #68859
Conversation
Co-authored-by: Will Browne <wbrowne@users.noreply.github.com>
@aocenas -- i think this is good to go, but will wait for your ✅ before merging :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM other than the switch
pkg/plugins/plugins.go
Outdated
@@ -165,6 +166,10 @@ func ReadPluginJSON(reader io.Reader) (JSONData, error) { | |||
switch plugin.ID { | |||
case "grafana-piechart-panel": | |||
plugin.Name = "Pie Chart (old)" | |||
case "grafana-pyroscope": // rebranding |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
case "grafana-pyroscope": // rebranding | |
case "grafana-pyroscope-datasource": // rebranding |
and subsequently the Phlare<>Pyroscope rebranding -- hardcoded alias
test
Looks like this works, don't really understand the code well enough to comment on that but seems like there was discussion enough about that already. Just wondering why |
all normal plugins end with their plugin type... typically |
This PR renames the builtin "phlare" datasource to "grafana-pyroscope-datasource" and adds registers an alias in the plugin registry. This will keep existing settings working while allowing us to rebrand the plugin.
Depends on #67867, starts to address #17186
Alternative to:
#67847
#67490