bmcweb/docs/DBUS_USAGE.md

1 # dbus usage
3 The following are guidelines for bmcweb's use of DBus to construct Redfish
6 - Do not require (ie set 500 internal error on) an implementation present a
7   property that wasn't in the first commit of the interface unless it can be
8   verified that _all_ OpenBMC implementers of the interface support that
10 - If an implementation presents a property that doesn't match the type specified
11   by the interface at any version, it shall be reported as a 500 error.
12 - If the DBus interface definition has an "unknown" or "unspecified" value,
15 - All DBus interfaces on all object paths are optional. An object missing an
16   interface is never an error, and shall simply omit the relevant properties
18 - bmcweb will code to the DBus interface itself. This means that daemons are
19   expected to handle functionally bad, but DBus-correct input in their own
21   duplication in input processing between the various user-facing daemons.
22 - There are interfaces for which there is an expectation that there will only