As far as concat goes, I wouldn't call my concat resource and my
concat::fragment resource by the same name. In theory it shouldn't
break anything, but...
On Thu, Nov 3, 2011 at 12:20 PM, Douglas Garstang
wrote:
> Actually I can. That's sweet! Thanks!
>
> On Thu, Nov 3, 2011 at 12:10 PM, Dou
Actually I can. That's sweet! Thanks!
On Thu, Nov 3, 2011 at 12:10 PM, Douglas Garstang
wrote:
> Just from looking at the example there, it doesn't appear that I can
> call sysctl::conf more than once That's what I like about concat,
> ie each module that needs to add to it can do so indi
Just from looking at the example there, it doesn't appear that I can
call sysctl::conf more than once That's what I like about concat,
ie each module that needs to add to it can do so individually.
Doug.
On Thu, Nov 3, 2011 at 12:04 PM, Mark Christian wrote:
> Can't speak to concat, but you
Can't speak to concat, but you might consider using augeas for managing
/etc/sysctl.conf. There is an excellent example of this at:
http://projects.puppetlabs.com/projects/1/wiki/Puppet_Augeas , see "Working
Examples"
> -Original Message-
> From: puppet-users@googlegroups.com [mailto:p
On 12 June 2011 20:21, Markus Falb wrote:
> I also tried with 0.25.5 and noticed that your module does not work.
> All autorequire stuff does not work. It seems like things like
>
> if catalog.resources.find_all { ... }.empty?
>
> is always true. I have no clue why.
It's because "catalog.resour
On 19.5.2011 01:01, Trevor Vaughan wrote:
> All,
>
> I'd love to get feedback on a module that turns R.I. Pienaar's file
> concatenation idea into a native type.
>
> The code is located at the Onyx Point Github:
> https://github.com/onyxpoint/pupmod-concat
>
> We found that using this instead
On 19.5.2011 01:01, Trevor Vaughan wrote:
> All,
>
> I'd love to get feedback on a module that turns R.I. Pienaar's file
> concatenation idea into a native type.
>
> The code is located at the Onyx Point Github:
> https://github.com/onyxpoint/pupmod-concat
>
> We found that using this instead
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
> After an hour or three of hacking, I've managed to add the insync? checks to
> both the build and fragment types. It's the first time I've ever really
> messed with types and providers, so it's very ugly (and probably has bugs),
> however I'm
Currently, the way that I'm preventing this is by bookending the
concat_build with a file object.
Basically:
concat_build { 'foo': target => '/etc/foo' }
file { '/etc/foo': checksum => md5, owner, mode, etc }
something { 'bar': subscribe => File['/etc/foo'] }
It's not elegant, but, in mos
Thanks for the patch set!
Feel free to add a pull request on GitHub, that way I can also just
pull into a branch.
Trevor
On Thu, Jun 2, 2011 at 11:25 AM, James Turnbull wrote:
> Greg Sutcliffe wrote:
>> Hi again,
>>
>> After an hour or three of hacking, I've managed to add the insync?
>> checks
Greg Sutcliffe wrote:
> Hi again,
>
> After an hour or three of hacking, I've managed to add the insync?
> checks to both the build and fragment types. It's the first time I've
> ever really messed with types and providers, so it's very ugly (and
> probably has bugs), however I'm happy to share my
Hi again,
After an hour or three of hacking, I've managed to add the insync? checks to
both the build and fragment types. It's the first time I've ever really
messed with types and providers, so it's very ugly (and probably has bugs),
however I'm happy to share my patches. Would that be best a)
Hi Trevor,
I'll add my thanks to the pile, this is pretty awesome stuff! I compared the
--graph results with the old concat moule, and this one - impressive
difference :)
As Larry says, the fact that it executes Concat_build on every run is a
stopper for us, since the dependant services get re
Hi Larry,
Unfortunately, no.
We didn't implement a insync? check since we just needed to overwrite
the target files anyway.
This is something that appears to be on the todo list as Puppet Labs
pulls this into the core.
We might beat them to it, but it's doubtful at this time.
Thanks!
Trevor
Hi Trevor
Thanks for the module.
I've been testing out the concat module, thanks, but the only issue I see is
files keep getting 'executed successfully' each round.
Is there any way to not have it do this? I haven't really looked that your
ruby logic yet.
--
You received this message because
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks, I hope you like it!
The ordering approach was a bit troublesome but we needed extreme flexibility
for various types of file targets so this is what we ended up with.
Trevor
On 05/18/2011 07:10 PM, R.I.Pienaar wrote:
>
>
> - Original M
- Original Message -
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> All,
>
> I'd love to get feedback on a module that turns R.I. Pienaar's file
> concatenation idea into a native type.
>
> The code is located at the Onyx Point Github:
> https://github.com/onyxpoint/pupmod-conca
17 matches
Mail list logo
