David,
Thanks for explanations and insight. I'll sit tight and keep an eye
out for updates to the Augeas type.
All the best,
Adam
On Jan 16, 1:18 pm, David Lutterkort wrote:
> On Fri, 2009-01-16 at 08:08 -0800, windowsrefund wrote:
> > I'll list current limitations
Peter,
Check out David Lutterkort's responses to my 2009-01-16 thread
entitled "[Puppet Users] Work in progress: Using augeas to manage /etc/
exports"
Best,
Adam
On Jan 18, 7:16 am, Peter Meier wrote:
> Hi
>
> > There is, as far as I can tell, no way to make Augeas *not* do
> > anything if a n
I don't see this information on the Type Reference page so I'm hoping
someone can provide an example of how to specify a package version
when the yum provider is used.
Thanks
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google G
out there?
Best,
Adam
On Jan 24, 9:15 pm, RijilV wrote:
> 2009/1/24 windowsrefund
>
>
>
> > I don't see this information on the Type Reference page so I'm hoping
> > someone can provide an example of how to specify a package version
> > when the yum pr
Generally speaking, you should be managing files in the sources.list.d
directory instead of managing lines in a single file.
also (generally speaking), you can
apt::source {
foo:
ensure => present;
bar:
ensure => absent;
}
The "style guide" frowns upon this syntax but it is far su
<%= eval "macaddress_" + my_lan1 %>
That will return the appropriate fact based on the value of my_lan1
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet
plugin aside, I strongly suggest not settling for YAML as a backend for
Hiera since you're basically ending up with the same problem you were
probably trying to solve; managing data in files. Sure, they're "different"
files but still files. You may as well keep the data in your Puppet
manifests
You don't
You'd manage a static httpd.conf which includes from a conf.d directory
containing site-specific configs. At the end of the day you want a define
that allows you do work like this psuedo code:
http:site {
thisawesomesiteisenabledbydefault:;
thisisold: ensure => absent;
}
--
Yo
Personally, I'm not looking forward to dealing with this "deep merge" thing
at all and would like to see it ripped out. When someone takes the time to
properly organize their backend data along with a sane hierarchy, there's
no need for this kind of overhead.
--
You received this message bec
I suggest taking a few hours/days to go through the existing documentation.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroup
101 - 110 of 110 matches
Mail list logo
