Hello Foreman-Team ,
Myself vikas ,i been developing a plugin for the
Foreman ,the functionality of the plugin is that we can manage the puppet
from the foreman GUI itself so that we can create new puppet class files
and manifest to the required environment (production ,common ,…) it
simply act as a file manager for the puppetmaster i am almost done but i
am struck with it,as the puppet-master is in root folder i can't able
modify and take action on that folder from a Ruby Engine Controller ,
In Foreman it is by default importing the puppet
classes from the puppet-master itself , no other option is available to
import from the other location
So plz do suggest is my idea of creating a puppet file from is wrong ? or
is there any other way to work with it . Waiting for your suggestions .
Thanking Your
Vikas .K
You need to decide a way to give the appropriate permissions to the app
that's writing. That may mean:
-
Change permissions on the directories you're managing to allow the
app user (usually 'foreman') to write to it.
-
Change the user that the app runs as to give it more permissions (bad
idea).
-
Add a higher privileged process to perform the writes that the app
can make requests to. In Foreman, that's usually the smart proxy - it
typically uses sudo or group permissions to read/write files. You could
perhaps write a smart proxy plugin
(Smart-Proxy Plugins - Foreman)
that makes the changes, though it's a lot more work.
···
On 14/03/16 15:03, Vikas Kuppili wrote:
> Hello Foreman-Team ,
>
> Myself vikas ,i been developing a plugin for
> the Foreman ,the functionality of the plugin is that we can manage the
> puppet from the foreman GUI itself so that we can create new puppet
> class files and manifest to the required environment (production
> ,common ,..) it simply act as a file manager for the puppetmaster i am
> almost done but i am struck with it,as the puppet-master is in root
> folder i can't able modify and take action on that folder from a Ruby
> Engine Controller ,
–
Dominic Cleal
dominic@cleal.org
Thank You very much Dominic for your reply i will work on it, by hook or
by crook i will do that but i want to know ,the plug in am creating which
is used a file manager for the puppetmaster classes is it a good idea ? is
there will be any technical issues will arise for exposing puppetmaster
environment directory . which is in /etc/puppet/ folder .
···
On Monday, March 14, 2016 at 8:39:02 PM UTC+5:30, Vikas Kuppili wrote:
>
> Hello Foreman-Team ,
>
> Myself vikas ,i been developing a plugin for the
> Foreman ,the functionality of the plugin is that we can manage the puppet
> from the foreman GUI itself so that we can create new puppet class files
> and manifest to the required environment (production ,common ,..) it
> simply act as a file manager for the puppetmaster i am almost done but i
> am struck with it,as the puppet-master is in root folder i can't able
> modify and take action on that folder from a Ruby Engine Controller ,
>
> In Foreman it is by default importing the puppet
> classes from the puppet-master itself , no other option is available to
> import from the other location
> So plz do suggest is my idea of creating a puppet file from is wrong ? or
> is there any other way to work with it . Waiting for your suggestions .
>
>
> Thanking Your
> Vikas .K
>
