FlexMeasures / flexmeasures / 35152602228

86%

push

github

Add `flexmeasures show automations` to list and inspect automations (#2533)

* Add `flexmeasures show automations` to list and inspect automations

The CLI could create, edit, delete and run automations, but not show them,
so the ID which `edit automation`, `delete automation` and `jobs run-automation`
expect had to be looked up in the UI, the API or the database.

Without --id, all automations are listed, inactive ones included.
With --id, one automation is shown in more detail: its recurrence in words,
its timezone, cursor, data generator, parameters, and the sensors it reads
from and writes to. An automation whose sensors no longer resolve still shows
its other details, which are often what is needed to work out why they do not.

Closes #2529

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

* docs/changelog: record `flexmeasures show automations`

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

* Address review: eager-load assets, name the automation, and pin down the cells

Listing automations dereferenced each automation's asset for the table's
Asset column, which the lazy relationship turned into a query per asset.
The rows now load their asset with them.

A schedule automation's `AutomationSensorsUnknown` message names its asset
rather than itself, so printing it bare did not say which automation broke
when an asset carries several. The command now names the automation.

Two assertions could not fail: the Type cell was checked by substring
against a whole row, which the automation's own name ("Day-ahead PV
forecasts") already satisfied, and no test created more than one
automation, so the listing's promised order by asset and then by ID was
never exercised. The listing cells are now read by column, and a new test
creates three automations across two assets, out of order.

The type test now creates a real scheduling automation rather than writing
an unsupported type onto a forecasting one, and the deta... (continued)

37 of 37 new or added lines in 1 file covered. (100.0%)

19252 of 22490 relevant lines covered (85.6%)

0.86 hits per line