Cloning and changing plugins whithout forking the whole project

#1

Hello there.

For the typical “BigCustomer you can’t say no” we would like to change the behavior of a couple of plugins but without forking the whole original code.

What are the steps to do to make the clone a new plugin (a pointer to the appropriate documentation is fine).

Until now my attempts generated 404:

system.js:4 Uncaught (in promise) Error: Fetch error: 404 Not Found
at system.js:4

Thank you in advance.

0 Likes

#2

There is no way to modify a core part without fork and rebuild

0 Likes

#3

Wow.

Sator arepo tenet opera rotas

0 Likes

#4

OK, since forking was the whole option, I forked. We will merge from master and deploy the whole grafana as a package for the distribution.

BTW, for those wondering, I did the following:

Cloned the table directory in another directory, gave it the same name as the new plugin-id.
Changed some class name (just to be sure to avoid conflicts)
Rebuilt frontend,
Restarted grafana.
(and now happy hacking to me).

0 Likes