On 03/01/2017 05:28 PM, Alexander Bokovoy wrote:
On ke, 01 maalis 2017, Simo Sorce wrote:
> My take is: cut API/UI work, and do the underlying infrastructure work
> for the widest set of serves/clients possible instead.
> It is much more important to get the underlying gears done than to add
> UI candy, that can be delayed.
I agree, we just have to come to agreement of *which* gears are really
Indeed, but adding attributes to ipaConfig and the ID Views is not hard,
it is a matter of extending two objectclasses instead of one ... if we
decide that Id Views are a good abstraction point.
Adding the same attribute to ID View and to ipaConfig sounds logical to
Martin, if you want help with this, I can implement ID View-related
parts. SSSD does have code to retrieve ipaConfig already, and it also
has support for reading ID View associated with the host. The resulting
value wouldn't end up in the same place, though, but this is something
to handle on SSSD side.
I was thinking about this at night (insomnia FTW) and it is actually
pretty easy to extend ID view with the same attribute (see my other
reply to Simo). Given the UI will be pretty dumb, we just can add the
new attribute to the ID view object and a common code will be
responsible for validation of changed values.
Manage your subscription for the Freeipa-devel mailing list:
Contribute to FreeIPA: http://www.freeipa.org/page/Contribute/Code