diff options
| author | Patrick Williams <patrick@stwcx.xyz> | 2022-12-07 16:14:21 +0300 |
|---|---|---|
| committer | Patrick Williams <patrick@stwcx.xyz> | 2022-12-07 16:14:26 +0300 |
| commit | dfa3fdc3dc1045babc67ecd7974c4d997006d9c4 (patch) | |
| tree | e2b076f0b29cf031dbada80cb9cc265e657ad7e9 /DBUS_USAGE.md | |
| parent | 6f284d244124c54db4d6fad6063b2aced18a844b (diff) | |
| download | bmcweb-dfa3fdc3dc1045babc67ecd7974c4d997006d9c4.tar.xz | |
format: reformat with latest openbmc-build-scripts
Reformat the repository using the latest from openbmc-build-scripts.
Add the `static/redfish` directory to be ignored by prettier since
these files come from elsewhere and having the ability to do a direct
diff is handy.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I74464d6f97047b4888a591e0d8a4f5ca970ac69e
Diffstat (limited to 'DBUS_USAGE.md')
| -rw-r--r-- | DBUS_USAGE.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/DBUS_USAGE.md b/DBUS_USAGE.md index 354a79bb79..75a36c7db3 100644 --- a/DBUS_USAGE.md +++ b/DBUS_USAGE.md @@ -10,15 +10,15 @@ schemas: - If the DBus interface definition has an "unknown" or "unspecified" value, detecting these will omit the property from the Redfish tree, in line with the Redfish specification. -- All DBus interfaces on all object paths are optional. An object missing an +- All DBus interfaces on all object paths are optional. An object missing an interface is never an error, and shall simply omit the relevant properties and/or actions from that Redfish Resource. -- bmcweb will code to the DBus interface itself. This means that daemons are +- bmcweb will code to the DBus interface itself. This means that daemons are expected to handle functionally bad, but DBus-correct input in their own - process, and return appropriate return codes. This is done to reduce the + process, and return appropriate return codes. This is done to reduce the duplication in input processing between the various user-facing daemons. - There are interfaces for which there is an expectation that there will only - ever be one producer in the project (ex bmc networking, user management). In + ever be one producer in the project (ex bmc networking, user management). In these cases, it is desirable to call the daemon by well known name directly. Bmcweb APIs should call the mapper in cases where it's reasonably expected that multiple implementations exist (ex, CPU management, Sensors). |