You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The NetworkManager connectivity check interval is 3600 seconds by default. Changing that requires editing config.json. It would be great if this could be turned into a (Balena Cloud) variable, eg. BALENA_SUPERVISOR_NETWORK_MANAGER_CONNECTIVITY_CHECK_POLL_INTERVAL.
I don't think that the other NetworkManager connectivity check parameters (URL and response) are that relevant that they also need their own variable. Providing 0 for BALENA_SUPERVISOR_NETWORK_MANAGER_CONNECTIVITY_CHECK_POLL_INTERVAL could for example be interpreted as "do not do connectivity checks".
The text was updated successfully, but these errors were encountered:
Hi @everhardt thanks for the feedback - it's a totally valid request. All config.json variables are meant to be exposed via the supervisor/SDK/balenaCloud. In the meantime we have been using tools like configizer, which I suspect have just delayed this work getting done by providing a workaround.
Thanks for the quick reply @alexgg! Probably superfluous to say: using the configizer on a fleet of devices that normally have the VPN disabled and aren't always online is still quite a hassle to do and keep track of.
The NetworkManager connectivity check interval is 3600 seconds by default. Changing that requires editing config.json. It would be great if this could be turned into a (Balena Cloud) variable, eg.
BALENA_SUPERVISOR_NETWORK_MANAGER_CONNECTIVITY_CHECK_POLL_INTERVAL
.I don't think that the other NetworkManager connectivity check parameters (URL and response) are that relevant that they also need their own variable. Providing
0
forBALENA_SUPERVISOR_NETWORK_MANAGER_CONNECTIVITY_CHECK_POLL_INTERVAL
could for example be interpreted as "do not do connectivity checks".The text was updated successfully, but these errors were encountered: