Renaming Datasources via Provisioning

You can have intrinsically correct provisioning configs with names differing from the names in Grafana. These should not lead to a crash on start but to expectable behaviour. The UID is the identifiying property of data sources, and so it should be possible to rename them by provisioning API. It doesn't stand to reason that it isn't possible this way, as it is possible using different means. I believe it is very easily possible to implement this without braking existing configuration. Above this line... https://github.com/grafana/grafana/blob/641a47c71dbdd4826638ebbdbd81791624a8aad7/pkg/services/provisioning/datasources/datasources.go#L66 ...you could query for the data source using the UID if it is provided (as it is optional but the name isn't and has to be unique, you also have to do the query by name. But you *can also* query by UID if it is provided.) If the query by UID yields a result, you can do the update route instead of the create route, which should be all to enable renaming. **Considerations** * Name provided but no UID - already works and would continue to work as new code only gets activated on a provided UID. * Old name provided but new UID - The query by UID would yield no result, as it doesn't exist yet. After that it would continue like it presently already does. * New name but old UID - UID query would yield result and new behaviour would kick in. This is the FR. * Old name and old UID - UID query would yield result but: if this just triggeres the same update as an existing name would, as per now, again, this should be no problem. **Who is this feature for?** Everyone who gets into the situation of wanting to rename a data source and using your file provisioning interface.