One-way dbus properties
Ratan Gupta
ratagupt at linux.vnet.ibm.com
Tue Apr 30 16:10:19 AEST 2019
Hi Adriana,
How is it different from readonly property, so suppose there is a object
which implements this interface.
when this object gets created, as part of creation we can set the
property, but after object creation user can,t set
the property.
Am I missing something here?
Ratan
On 24/04/19 8:47 PM, Adriana Kobylak wrote:
> Wanted to get thoughts on how attempting to clear one-way dbus
> properties should be handled.
>
> There are some properties like Field Mode that are intended to be
> one-way, meaning that you can set them but not clear them:
>
> -
> https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/xyz/openbmc_project/Control/FieldMode.interface.yaml
> description: >
> Keeps track of whether the BMC is in field mode. Enabling
> field mode
> is intended to be a one-way operation.
>
> If there's a call to clear the property value, currently this is a
> no-op and the REST call returns success but the value is not changed.
> Should an error be returned to the user? It's like a read-only
> property but only after it's being set the first time.
>
More information about the openbmc
mailing list