This patch finally introduces a data model for defining animation-scenarios and -steps. This yields the following features:
Scenarios can be loaded from arbitrary Python modules or files. For example, you can use grafanimate --scenario=acme.scenarios:foobar to load scenario data from the foobar variable within the acme.scenarios module. You can also address arbitrary files, by using an invocation like --scenario=/path/to/acme/scenarios.py:foobar.
The grafana-url and dashboard-uid parameters can optionally be defined within the scenario description. For an example, please have a look at scenarios.py#L34-L35. When using the built-in scenario playdemo, it essentially brings the invocation down to grafanimate --scenario=playdemo.
Hi.
This patch finally introduces a data model for defining animation-scenarios and -steps. This yields the following features:
grafanimate --scenario=acme.scenarios:foobarto load scenario data from thefoobarvariable within theacme.scenariosmodule. You can also address arbitrary files, by using an invocation like--scenario=/path/to/acme/scenarios.py:foobar.grafana-urlanddashboard-uidparameters can optionally be defined within the scenario description. For an example, please have a look atscenarios.py#L34-L35. When using the built-in scenarioplaydemo, it essentially brings the invocation down tografanimate --scenario=playdemo.With kind regards, Andreas.