Can the data source be provisioned by version number?

[bunkiedc]

We use provisioning for our data sources, but I've notice that we get the latest one each time a new user gets added. I would like to be able to stage first in dev before allowing it into production, but I don't see a way of including a version (like the graphiteVersion) in my provisioned yaml file. Is there a way?

[yesoreyeram]

Can you explain more? What do you mean latest every time? How do you provision etc?

[bunkiedc]

I provision from a yaml file. When a user is created, it deploys the grafana environment using the provisioned data source. But it always picks the latest version available, instead of being able to have it in the provisioned yaml file. I noticed that graphite has this capability e.g. graphiteVersion= "1.1". I'd like to be able to do the same with infinity. I now have new users using 2.11.4, and older ones using 2.11.3, so I'd like to be able to validate the updates before having the production environment use the latest.

[yesoreyeram]

In grafana cloud or on-pren deployment? Can you share the provisioning config? Provisioning is only for datasource not for plugin. So I suspect something wrong with your setup.

[yesoreyeram]

And datasources doesnt have version at all. Only plugins will have version

[bunkiedc]

I’m not at my computer at the moment, I can sent it tomorrow if it’s needed. What’s the 2.11.4 then?  The Manifest shows 2.11.3 on some of my deployments and some with 2.11.4.  This is the infinity plugin we’re talking about right?I’m deploying on-prem. Nothing is broken, it’s working fine. I just wanted to control what gets installed and when. David714-476-2692On Nov 28, 2024, at 14:02, Sriram ***@***.***> wrote: And datasources doesnt have version at all. Only plugins will have version —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[bunkiedc]

Here's the yaml I'm using.

apiVersion: 1
datasources:
  - id: 2
    name: "Infinity"
    type: "yesoreyeram-infinity-datasource"
    version: 1   
    orgId: 1
    uid: "myUIDxxxxxx"
    isDefault: "false"
    editable: "false"
    readOnly: "true"
    basicAuth: "false"
    basicAuthUser: ""
    jsonData:
      allowedHosts: 
       - "http://myHost:myPort"
      global_queries: []
      secureQueryName1: ""
    secureJsonData:

What I've seen as far as graphite is concerned, is:

apiVersion: 1
datasources:
  - name: Graphite
    type: graphite
    access: proxy
    url: http://localhost:8080
    jsonData:
      graphiteVersion: '1.1'    <---- this is the version number to use

[yesoreyeram]

graphite does have version where infinity is talking to API and it doesn't have version.

To understand your question better, Where do you see 2.11.4?

[bunkiedc]

When each user is created, it creates a plugin directory there as well, in in that is the yesoreyeram-infinity-datasource folder, and in that is the MANFEST file. And within that you see the version: 2.11.4 (or 2.11.3 on my older users). Since those seem to match what the repo is showing as released, I assumed we are alway getting "latest" when a user is created.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

{
  "manifestVersion": "2.0.0",
  "signatureType": "grafana",
  "signedByOrg": "grafana",
  "signedByOrgName": "Grafana Labs",
  "plugin": "yesoreyeram-infinity-datasource",
  "version": "2.11.4",
  "time": 1732277483924,
  "keyId": "7e4d0c6a708866e7",
  "files": {
    "CHANGELOG.md": "879173a5b9df7a2075ae6023f3d492da0346bd540f0cdac60c90002b62ac60a3",
    "LICENSE": "85fb2c20b586ef9dc00ee5c41140e1cd59fdded9a0b24a9054b04e9f0f6b2977",
    "README.md": "351dea529ec76dc9b396ef8f29d4ec36cab5ace16040f42142f0c58427ee3a7d",
    "go_plugin_build_manifest": "b03936392060645df86485e2649ad6e65c14c6299ab6dee64fa7d3df3489f4af",
    "gpx_infinity_linux_amd64": "720c7d764875e7abb5d49332061196d443effa39867be6fcff5a1f95bc67bbd7",
    "img/aws.jpg": "e682ccc794708fd3eb32a3fb5e2bcccd8ff3b54f30eba2086fd1b28a82020d81",
    "img/homepage-bg.svg": "97ec32b2c542bcb63b7fa7659e42a876a5b9ec00aef7a486f2dc41b83d7d9eb8",
    "img/icon.svg": "e498b00e1cc3c9e8b65a2b8320b7d170c6da61d424fe5f3f3fdf9963204449ae",
    "img/oauth-2-sm.png": "9945bb307d5545369d50381acc97d48b4a98433831f14e99eb839f0970a91258",
    "img/slide-features.png": "58aba3b2f2d73ee99945cba9746463f0039d8afb5366ed8d42db62145b914d0f",
    "img/slide-rest-api.png": "cf72349768e0ccf19a856d86e97c8e67dcdadfcee49e73ae5acbe781c3ae0c79",
    "img/slide-series.png": "f7d523c39f9d4567974c37432f047e4e8944cb92dc2c9a4424757ce5e54dc3a7",
    "img/slide-variables.png": "8ed0cd7b1ac00bd2c7fa6e72c513b678c39ba7d63030f06e8695cb1d352e3b34",
    "module.js": "aad3b2ec6a1b1649ee2d6a88c795e918b27d9064703e6607f6f81e3c00a4c846",
    "module.js.LICENSE.txt": "4cc2b646a9dd57535489632cb3201bbbf7731ce1aa626b16c7118b71275f9a8f",
    "module.js.map": "d14b161a4a84e3530f220351a2365a27df1941fb6adde34bddd00cccf44c09f5",
    "plugin.json": "9acdcb51b7ea2049e82d369c4fa0bb66e0c0a97e67d2bec7a482445b296dbba4"
  }
}
-----BEGIN PGP SIGNATURE-----
Version: OpenPGP.js v4.10.11
Comment: https://openpgpjs.org

wrkEARMKAAYFAmdAdOwAIQkQfk0ManCIZucWIQTzOyW2kQdOhGNlcPN+TQxq
cIhm56uJAgkB4i6BSuU20JJTp5Dov3HxvN6eUK2SYJqJG7sErNbWRmSx2arZ
NlStnaVywPdU0zREf2saNrUv+3D2SaQ//miKd6oCCQDqiCiilfQGWWMIoCde
CnOOTnLwuLr3T36N1SJ2762tLE7toiMhSwzqHjwSRD2ecFw0OqsE1q9XjUsb
hJHpyzZ9qA==
=/nle
-----END PGP SIGNATURE-----

[yesoreyeram]

The provisioning you showed is for datasources. Not for plugins.

The plugins version depends on how you install it. If you don't specify the version during installation, it will always get the latest version. Refere infinity plugin installation document or any other plugin installation document.

Also user creation doesn't matter here.

[bunkiedc]

the user creation I'm referring to is an entire grafana stand-alone environment, with each having their own config, so it does matter.
I'm confused now. The datasource is what is changing right... from 2.11.13 to 2.11.14. That's what I'm trying to control by version. Is that possible or not? I haven't found anything in the documentation that specifies how that is achieved.

[yesoreyeram]

The version of the plugin you want to use can be controlled by how you are installing the plugin to your instance. Refere the following guidelines for various installation methods https://grafana.com/docs/plugins/yesoreyeram-infinity-datasource/latest/setup/installation/

[bunkiedc]

@yesoreyeram thanks for the link... I totally missed the docker part that shows using GF_INSTALL_PLUGINS with the zip file.

I'm using the grafana method where I'm putting these directives in the config.env file.

With adding the directive below, it comes back now saying that:

Error: ✗ 404: /plugins/https:/github.com/grafana/grafana-infinity-datasource/releases/download/v2.11.4/yesoreyeram-infinity-datasource-2.11.4.zip/versions does not exist (Grafana v11.1.4 linux-amd64)

original directive

GF_INSTALL_PLUGINS="yesoreyeram-infinity-datasource"

new directive

GF_INSTALL_PLUGINS="https://github.com/grafana/grafana-infinity-datasource/releases/download/v2.11.3/yesoreyeram-infinity-datasource-2.11.3.zip,yesoreyeram-infinity-datasource"

Any ideas on how to get that to find the download file?

[yesoreyeram]

At the bottom of the plugin catalog you can find this. https://grafana.com/grafana/plugins/yesoreyeram-infinity-datasource/?tab=installation

alternatively (least preferred option) in github release page you can find this https://github.com/grafana/grafana-infinity-datasource/releases

[bunkiedc]

thanks again for the info!
The problem was a semicolon is needed between the download part and the install part, not a comma.

GF_INSTALL_PLUGINS="https://github.com/grafana/grafana-infinity-datasource/releases/download/v2.11.3/yesoreyeram-infinity-datasource-2.11.3.zip;yesoreyeram-infinity-datasource"

ALL working now, thanks for you patients and help.