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
A static base header is always used - with "log_debug = off". The only way to modify this property to enable extra logging is to change the redocks.conf file directly. The issue with this is that further PATCH requests to /v1/device/host-config will overwrite this change with the header here again:
From my understanding we are deliberately limiting what redsocks configuration options can be modified via this endpoint to try to prevent mistakes being made, which could lead to unreachable devices - for example "local_port = 12345 is set, so that the iptables rules and redsocks port match." - however "log_debug = on" is a safe one to allow - so maybe its worth enabling that?
The text was updated successfully, but these errors were encountered:
Right now the
/v1/device/host-config
endpoint is limited to inly modifying a subset of the redocks configuration fields:balena-supervisor/src/host-config.ts
Line 35 in 963f43c
A static
base
header is always used - with "log_debug = off". The only way to modify this property to enable extra logging is to change theredocks.conf
file directly. The issue with this is that further PATCH requests to/v1/device/host-config
will overwrite this change with the header here again:balena-supervisor/src/host-config.ts
Line 20 in 963f43c
From my understanding we are deliberately limiting what redsocks configuration options can be modified via this endpoint to try to prevent mistakes being made, which could lead to unreachable devices - for example "local_port = 12345 is set, so that the iptables rules and redsocks port match." - however "log_debug = on" is a safe one to allow - so maybe its worth enabling that?
The text was updated successfully, but these errors were encountered: