Describe the bug

The tedge config c8y.device.csr_path is not supported whilst the c8y.device.key_path and c8y.device.cert_path are.

For example when trying to set c8y.device.csr_path via tedge config set, it results in an "Unknown key" error.

tedge config set c8y.device.csr_path /etc/tedge/device-certs/example_dev_test0001-test1.csr
error: invalid value 'c8y.device.csr_path' for '<KEY>': Unknown key: 'c8y.device.csr_path'

For more information, try '--help'.

Workaround

The --output-path can be used to control where the CSR file is written to.

tedge cert create-csr --device-id "$DEVICE_ID" --output-path "$CSR_PATH"

To Reproduce

The error can be reproduced by simply trying to set c8y.device.csr_path to any value.

tedge config set c8y.device.csr_path /etc/tedge/device-certs/example_dev_test0001-test1.csr

Expected behavior

The device.csr_path should be able to be specified per cloud profile (like the c8y.device.cert_path currently is).

Screenshots

Environment (please complete the following information):

• OS [incl. version]: Any
• Hardware [incl. revision]: Any
• System-Architecture [e.g. result of "uname -a"]: Any
• thin-edge.io version [e.g. 0.1.0]: 1.4.3~165+ge0c07f1

Additional context