chore: add plugin provisioning script for E2E tests

[vickyyyyyyy]

In order to run our E2E tests, we require the provisioning yaml file to be in the <rootDir>/provisioning folder: https://github.com/grafana/grafana/blob/1d689888b0fc2de2dbed6e606eee19561a3ef006/packages/grafana-e2e/cypress/plugins/readProvisions.js#L12

This is already set up for the build but if we want to debug the tests locally, we would also need this set up.

Adding this script so it can be automated and copied over in our plugins (or if there is some way to export this and use this actual script?) so in the package.json file, we can do something like:

{
   "provision-plugin": "bash provision-plugin.sh datadog"
   "e2e:dev": "yarn provision-plugin && grafana-e2e run"
}

This script expects the provisioning file name to be passed in so we only grab the one yaml file needed instead of the whole repository.

First time set up

File name not passed in

Invalid file name

Valid file name

Non-first time set up

File name not passed in

Invalid file name

Valid file name

[scottlepp]

You could use node instead of bash: then from scripts: "node run ./provision.js"

But...I just do this (assumes you have the provisioning repo cloned in your workspace): https://github.com/grafana/jira-datasource/blob/master/DEV-GUIDE.md

[vickyyyyyyy]

You could use node instead of bash: then from scripts: "node run ./provision.js"

But...I just do this (assumes you have the provisioning repo cloned in your workspace): https://github.com/grafana/jira-datasource/blob/master/DEV-GUIDE.md

Yeah, I was thinking about symlinking instead but thought it would be nice to have something automated instead so you don't need to set it up for each plugin. Especially since I sometimes have multiple copies of the same repo/plugin for testing different things 😬

[vickyyyyyyy]

Closing - not needed for now