[enhancement]: Evaluate blocking of access to common.custom config for foreign adapters #3093
Description
No existing issues.
- There is no existing issue for my request.
Description
We had a discussion that adapter lorawan modifies / creates / deletes custom configuration of mqtt-client instance.
lorawan creates mqtt-client custom config at states bypassing the jsonCustom.json configuration and uses attributes evaluated ("grabbed") at time x. This for sure will miss future changes.
I suggest to evaluate whether we should block the possibility that any other adapter than admin (which is definitly using the adapter's jsonConfig.json config) and the "owing" adapter (mqtt-client at this example) is allowed to write to the custom config data dor mqtt-cleint.x
Why?
Accessing data in a way not expected by the owning adapter and the kernel could lead to unexpected errors.
How?
No response