We are looking at doing a partial migration from Grafana v6 to Grafana v7 – since some of the features and plugins we use are not really compatible with v7. Therefore we are planning to run v6 and v7 side by side. At the same time, we’d prefer to not “fork” the backend PostgreSQL database, but instead keep a single, consistent, datastore that both instances use. (I can go into the reasons here, but for example we’d like to keep a consistent user database)
What is the likelihood that this would work across major versions? I actually did a quick experiment, having both v6.2.2 and v7.1.1 instances using a single Postgres database, and things seemed to work just fine. The only breakage I noticed was when saving an edited dashboard in v7, the respective dashboard would no longer load in v6. That kind of behavior is actually acceptable, since the v6 instance and v7 instances would primarily be accessed by different sets of orgs.
I assume the official answer is “don’t do that, it will break things”, but I thought I’d check what the specific gotchas are, and whether anyone has wise words to share on the topic.