fix: provider settings in top level field of configuration (#1161)

Configuration for some providers was given in the sub-field `provider_settings`
combining the settings of several providers. Pydantic does not understand
this very well and the configuration became cumbersome, especially in EOSdash.

All provider settings from the `provider-settings` sub-field are now lifted
to the top level field of the configuration.

The changes are automatically migrated in the configuration.

Signed-off-by: Bobby Noelte <b0661n0e17e@gmail.com>
This commit is contained in:
Bobby Noelte
2026-07-20 14:37:03 +02:00
committed by GitHub
parent 845191c0d0
commit 3bb0e02aed
44 changed files with 798 additions and 1061 deletions

View File

@@ -13,12 +13,10 @@ def pvforecast_instance(config_eos):
"general": {"latitude": 52.5, "longitude": 13.4},
"pvforecast": {
"provider": "PVForecastPVNode",
"provider_settings": {
"PVForecastPVNode": {
"api_key": "dummy-key",
"site_id": "test-site-123",
"forecast_days": 2,
},
"pvnode": {
"api_key": "dummy-key",
"site_id": "test-site-123",
"forecast_days": 2,
},
},
}
@@ -122,8 +120,8 @@ def test_request_forecast_inline_post_when_no_site(config_eos):
"general": {"latitude": 52.5, "longitude": 13.4},
"pvforecast": {
"provider": "PVForecastPVNode",
"pvnode": {"api_key": "k", "site_id": None},
"planes": [{"surface_tilt": 30.0, "surface_azimuth": 180.0, "peakpower": 5.0}],
"provider_settings": {"PVForecastPVNode": {"api_key": "k", "site_id": None}},
},
}
)