Configuration API for Thing name, MQTT username, and password

[dcgaws]

In production, customer firmware won’t read the device Thing name, MQTT username, and password (if any) from static strings in the code. Instead, elements such as those will be read from configuration (i.e. separate area of flash; EPROM; or etc.). We need to:

• Define a configuration storage interface
• Reference it from our other libraries.
• Port it to a handful of representative platforms, including embedded Linux and at least two MCU architectures.
• If secure storage is available on the developer board or platform in question, store confidential configuration elements such as the MQTT password there.
• Not count solely on static analysis tools to find buffer overflows in our various serialization code (for example, Jobs and MQTT), since dynamic configuration values will be defined after an embedded module has been deployed.

[cmbpereira]

Hi everyone,

I feel the need for a feature like this. I want to use the serial number saved in EEPROM as Thing Name.
What are the plans for this feature to be included in the project?

Thanks in advance