rolekit D-Bus API v2

Stef Walter stefw at
Wed Jul 2 06:23:51 UTC 2014

On 02.07.2014 08:17, Marius Vollmer wrote:
> Stephen Gallagher <sgallagh at> writes:
>> Roles are not meant to be "discoverable" (other than whether a
>> particular role is available for installation). These are going to be
>> a fixed, documented set of arguments unique to each role. We will do
>> input validation in the role implementation, but I'm not sure how (or
>> if) we could make those arguments discoverable (or if we'd want to).
>> The expectation here is that a client of the API would know which
>> attributes are needed for the role from the documentation.
> Hmm, ok.  So the role specific code would be pre-loaded into Anaconda
> and Cockpit somehow, and publishing a new role in a repository needs an
> update to both Anaconda and Cockpit?

Yes, I think that's the case. We need role specific UI code. This is
exactly the sort of thing we're building Cockpit module support for.

I really don't think we should try and reinvent debconf prompts.


More information about the server mailing list