So I have a module (svn) that has a fuction (svnserve) that when
invoked, looks something like this:
svnserve { dist:
source => "svn://foo/bar",
path => "/tmp/svn-checkout",
user => "user1",
pass => "secretpw"
}
And when defined under a node that''s included or inherited the
"svn"
module, everything is peachy. But I''m a noob, and that''s why
I''m
posting. When I try to assign these parameters via the dashboard, I''m
S.O.L.
I''ve applied the svn module (class in dashboard) to a node. Now I
want to specify what''s in place of dist, source, path, user, and
pass. I''ve tried parameters with names like the following:
source
svn::source
svn::svnserve::source
svnserve::source
svnserve.source
and a whole slew of other stupid ideas trying to get it to work once.
Can someone help me with this one? I''m sure I''m doing
something
stupid and a grand puppet virtuoso will point out the source of my
boondoggle with the brevity and completeness of a genius. Or else you
can''t do that via dashboard. Either way, I''d like to know
what I''m
messing up.
-TDS-
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Any guidance on this one? Anyone know how to set the variables in a module via dashboard? It''s obviously quite easy when using config files, and if it were up to me alone, that''s what we''d do. But in an enterprise environment, what you want isn''t always best for the organization''s needs. This is my only stumbling block at the moment. On Jul 19, 4:54 pm, TheDirtyScreech <matthew.ebersvil...@gmail.com> wrote:> So I have a module (svn) that has a fuction (svnserve) that when > invoked, looks something like this: > > svnserve { dist: > source => "svn://foo/bar", > path => "/tmp/svn-checkout", > user => "user1", > pass => "secretpw" > > } > > And when defined under a node that''s included or inherited the "svn" > module, everything is peachy. But I''m a noob, and that''s why I''m > posting. When I try to assign these parameters via the dashboard, I''m > S.O.L. > > I''ve applied the svn module (class in dashboard) to a node. Now I > want to specify what''s in place of dist, source, path, user, and > pass. I''ve tried parameters with names like the following: > > source > svn::source > svn::svnserve::source > svnserve::source > svnserve.source > > and a whole slew of other stupid ideas trying to get it to work once. > Can someone help me with this one? I''m sure I''m doing something > stupid and a grand puppet virtuoso will point out the source of my > boondoggle with the brevity and completeness of a genius. Or else you > can''t do that via dashboard. Either way, I''d like to know what I''m > messing up. > > -TDS--- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I''m looking for some guidance here as well. We migrated away from flat files to foreman for an ENC a couple of months ago. Since then, I''ve moved what parameter classes we had to kind of weird mash-ups.. I still set variables with foreman but I''ve always wondered how ENCs should be with parameter classes and definitions. Its odd that such a big feature (class parameters/definitions) would seemingly be overlooked in the documentation for ENCs like dashboard. On Jul 20, 7:52 pm, TheDirtyScreech <matthew.ebersvil...@gmail.com> wrote:> Any guidance on this one? Anyone know how to set the variables in a > module via dashboard? It''s obviously quite easy when using config > files, and if it were up to me alone, that''s what we''d do. But in an > enterprise environment, what you want isn''t always best for the > organization''s needs. This is my only stumbling block at the moment. > > On Jul 19, 4:54 pm, TheDirtyScreech <matthew.ebersvil...@gmail.com> > wrote: > > > > > > > > > So I have a module (svn) that has a fuction (svnserve) that when > > invoked, looks something like this: > > > svnserve { dist: > > source => "svn://foo/bar", > > path => "/tmp/svn-checkout", > > user => "user1", > > pass => "secretpw" > > > } > > > And when defined under a node that''s included or inherited the "svn" > > module, everything is peachy. But I''m a noob, and that''s why I''m > > posting. When I try to assign these parameters via the dashboard, I''m > > S.O.L. > > > I''ve applied the svn module (class in dashboard) to a node. Now I > > want to specify what''s in place of dist, source, path, user, and > > pass. I''ve tried parameters with names like the following: > > > source > > svn::source > > svn::svnserve::source > > svnserve::source > > svnserve.source > > > and a whole slew of other stupid ideas trying to get it to work once. > > Can someone help me with this one? I''m sure I''m doing something > > stupid and a grand puppet virtuoso will point out the source of my > > boondoggle with the brevity and completeness of a genius. Or else you > > can''t do that via dashboard. Either way, I''d like to know what I''m > > messing up. > > > -TDS--- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Tue, Jul 19, 2011 at 5:54 PM, TheDirtyScreech <matthew.ebersviller@gmail.com> wrote:> So I have a module (svn) that has a fuction (svnserve) that when > invoked, looks something like this:So I presume this is a custom define resource.> svnserve { dist: > source => "svn://foo/bar", > path => "/tmp/svn-checkout", > user => "user1", > pass => "secretpw" > } > > And when defined under a node that''s included or inherited the "svn" > module, everything is peachy. But I''m a noob, and that''s why I''m > posting. When I try to assign these parameters via the dashboard, I''m > S.O.L.Dashboard does not have the ability add resources, only set classes and top scope parameters. So, sorry you can''t set or override resource attributes directly. create_resource function can resolve some of these issues, but you need a wrapper class.> I''ve applied the svn module (class in dashboard) to a node. Now I > want to specify what''s in place of dist, source, path, user, and > pass. I''ve tried parameters with names like the following: > > source > svn::source > svn::svnserve::source > svnserve::source > svnserve.sourceThis is probably the best way for the moment: Dashboard: add class svn_wrapper add svn_wrapper to a node add parameter source="svn://foo/bar" In puppet you need a class similar to below: class svn_wrapper { svnserve { dist: source => $::source, } } You can''t have a default value in Puppet and expect dashboard to override the value magically. If you want the ability to set the value, you need some helper functions. I wrote a pick function to select the first value in priority: svnserve { dist: source => pick($::source, $svn::param::source, "svn://some/default") } This however isn''t very transparent, since you are mixing the source of data between dashboard, puppet class, and local defaults.> and a whole slew of other stupid ideas trying to get it to work once. > Can someone help me with this one? I''m sure I''m doing something > stupid and a grand puppet virtuoso will point out the source of my > boondoggle with the brevity and completeness of a genius. Or else you > can''t do that via dashboard. Either way, I''d like to know what I''m > messing up.I''m not sure if there are better options than the one suggested above, dashboard definitely needs a better way to store and set data in a hierarchy. Thanks, Nan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.