16.4 Configuration Errors

Go To Top

Return to Exception Handling

Configuration errors should fail early. Nodes, scripts, containers, and validation tools should validate required Configuration before they rely on it.

Configuration error handling should detect:

1. Missing required Configuration files.
2. Invalid Configuration format.
3. Missing required fields.
4. Invalid values.
5. Unsupported profile names.
6. Missing environment variables.
7. Invalid paths.
8. Invalid Topic names.
9. Invalid QoS profile references.
10. Invalid Node Identity or Node role values.
11. Conflicting Configuration values.

When a Configuration error occurs, the implementation should identify the Configuration source, the failing field or value where safe, and the reason the value is invalid. Error messages should avoid leaking secrets, credentials, or sensitive local values.

A Node that cannot validate required Configuration should publish Failed status where possible and exit. A script that cannot validate required Configuration should return a non-zero exit code. A container that starts with invalid Configuration should fail visibly rather than running in an undefined state.