rolekit D-Bus API v2

[Marius Vollmer]

Stephen Gallagher <sgallagh at redhat.com> 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?