commit | 1a891d32437863796137a239bebbf2be2884ebf1 | [log] [tgz] |
---|---|---|
author | Nan Zhou <nanzhoumails@gmail.com> | Mon Oct 24 23:51:41 2022 +0000 |
committer | Nan Zhou <nanzhoumails@gmail.com> | Tue Nov 15 20:28:32 2022 +0000 |
tree | 4d05d5c6da3b76e25c6997ad0c2ea951df93bb31 | |
parent | 219368bedb6a8607a50ec9ad9129478e45cdd68f [diff] |
User: add interfaces and errors for groups As proposed in the following design, [1] https://github.com/openbmc/docs/blob/master/designs/redfish-authorization.md The UserManager interface needs to expose new interfaces to add/delete secondary groups, which are then used to model Redfish roles and privileges. An implementation is in the follow code review, [1] https://gerrit.openbmc.org/c/openbmc/phosphor-user-manager/+/58143. Signed-off-by: Nan Zhou <nanzhoumails@gmail.com> Change-Id: I252e56dc03e694e3aedf3ae6fdda64edc947fc06
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.
This project can be built with meson
. The typical meson
workflow is: meson builddir && ninja -C builddir
.
The meson files used to handle the YAML files are automatically generated and found under the gen
subdirectory. When adding or removing YAML files, this must be regenerated. This can be done with the helper script found in the gen
subdirectory: cd gen && ./regenerate-meson
.
Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true
-Ddata_org_open_power=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir