One-way dbus properties

[Thomaiyar, Richard Marian]

Adriana,

What's the purpose of this property ? Why we are not using the same in 
RestrictionMode ? Any pointers when RestrictionMode::whitelist / 
blacklist will be used.

Reason: Defining new one, and planning to use Security::RestrictionMode 
itself to indicate that BMC system in not deployed (i.e. not in field), 
or deployed with certain restriction?

Let me know

Regards,

Richard

On 4/24/2019 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.
>