Mailinglist Archive: yast-devel (246 mails)

< Previous Next >
Re: [yast-devel] WebYaST: Vendor customization
  • From: "Duncan Mac-Vicar P." <dmacvicar@xxxxxxx>
  • Date: Fri, 14 Aug 2009 11:05:45 +0200
  • Message-id: <200908141105.45335.dmacvicar@xxxxxxx>
On Thursday 13 August 2009 18:39:25 Jiří Suchomel wrote:
On Thursday 13 of August 2009 18:16:02 Duncan Mac-Vicar Prett wrote:
On Thursday 13 August 2009 15:37:12 Jiří Suchomel wrote:
The reason to involve YaPI is different: SCR layer runs as root after
user passes the permissions checks, so it has rights to access the
scripts.

They are configuration items, not scripts, why should one need special
rights?

But someone has to really start or stop selected service, so at the end, we
need a root access to the system.

Jiri

Yes, that is why we hide YaPI or SCR calls in a model. But to know which
services are available (from vendors perspective, aka read the vendor config)
you don't need root, and if you did, then you need root to get the file
content, but there is no need to parse it at the root side.

so either you have

services -----------> dbus/YaPI/SCR -------------> rest-service
vendor.yml -----------> File.read -> YAML.parse -->

or, if the file really needs root permissions, you get

services -----> dbus/YaPI/SCR -------------------------------> rest-service
vendor.yml -----> dbus/YaPI/SCR (read content) -> YAML.parse -->

The configuration reading (and how it affects what the Service model returns
can be hidden in the same YaPI wrapper that simulates an ActiveRecord so for
example it returns results based on the vendor config.

Duncan
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >