On Wed, 2014-06-04 at 14:12 -0700, Ethan Brown wrote:
>
> 2468 (PUP-2079): Add mechanism to allow template files to be copied
> without getting parsed
> - This is a modules/forge team, Adrien to ping everybody remotely
> related to the forge
> - The changes that were blocking this have landed
On Tue, 2014-04-29 at 00:35 -0700, Daniele Sluijters wrote:
> I'm with Trevor here. A Face to interact with environments and query
> for state would be really helpful to debug such issues or force a
> refresh.
O/T: Are there any docs/guides around writing puppet faces?
Thanks,
R.
--
You recei
Are hashes as property values out of the question?
eg.
ensure => {
installed => true,
version => '1.2.3',
held => true,
bikeshed => 'green',
}
R.
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and
On 06/15/2011 09:11 AM, R.I.Pienaar wrote:
Below is a edit taking your 66 line changelog down to a usable 25 lines
by removing all the purely testing related lines, the merge lines and maint
lines.
I think this is already a huge improvement. Changelogs are what users use
to determine the suita
On 11/05/11 16:38, Todd Zullinger wrote:
> Robin Bowes wrote:
>> Any chance you could create separate -testing repos for the release
>> candidates, and only put released versions in the "main" repos?
>
> I don't plan to do so, no. My repos are intended for tes
On 10/05/11 15:31, Todd Zullinger wrote:
> Robin Bowes wrote:
>> Are you going to be updating your repo to include this?
>
> Eventually, just been busy. If you look at the changelog from rc1,
> you'll see that 2.6.8 final only adds some things to tests, so for an
> e
On 27/04/11 22:30, Jacob Helwig wrote:
> This release addresses issues with the Puppet 2.6.x series.
>
> Bug #4884:
>
> Shell exec provider that executes code as a raw shell script
>
> Bug #5670:
>
> Failed resources don't improperly trigger a refresh
>
> Feature #2331:
>
> New macports
On 14/04/11 22:59, Todd Zullinger wrote:
> Matt Robinson wrote:
>> This release addresses issues with the Puppet 2.6.x series.
>
> For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
>
> http://tmz.fedorapeople.org/repo/puppet/
>
> Packages for EL 4 - 6 and Fedora 13 - 15 a
On 07/04/11 11:51, Peter Meier wrote:
> Hi
>
>> +install -Dp -m0644 %{confdir}/%{name}.logrotate
> $RPM_BUILD_ROOT/%{_sysconfdir}/logrotate.d/puppet-dashboard
>
> you should prefix that with the creation of logrotate.d (as usual in
> RedHat based spec files deploying logrotate files). So this sho
On 05/04/11 18:44, Matt Robinson wrote:
> It would be great if there was some WHY explanation in the commit message.
>
Yes, I was looking for that. No issues, just curious.
R.
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to th
I'm having trouble getting git mail_patches to work on my
tickets/2.6.x/6718 branch, so I'm sending this patch manually.
This fixes the bug (#6718) whereby it is not possible to create a new
service.
diff --git a/lib/puppet/provider/service/runit.rb
b/lib/puppet/provider/service/runit.rb
index 03
On 23/09/10 16:58, James Turnbull wrote:
> Mathias Gug wrote:
>> Hi,
>>
>> Excerpts from Markus Roberts's message of Thu Sep 23 00:53:27 -0400 2010:
>>> I inadvertently left some tickets off the "Ready for Testing" list:
>>>
>>> #2224 (http://projects.puppetlabs.com/issues/2224) Add an Expire
>>> p
On 20/09/10 17:53, Nigel Kersten wrote:
> Maybe we add this too ? http://projects.puppetlabs.com/issues/3933
>
> "Option to make Puppet fail as soon as a resource fails."
Hmmm, not sure - feels a bit different to me, and possibly warrants a
separate switch (--halt-on-error).
>
> How would we d
On 19/09/10 19:59, Peter Meier wrote:
>> Would it be possible to make puppet throw an error when this happens?
>
> I don't think this is a good idea. I'm using this a lot to tweak what
> parts of manifests are applied.
That doesn't mean it's a good thing! :)
I'd really like to be able to sanity
Hi,
I seem to remember having this conversation before, but I have lost
count of the number of times I've been bitten when I've either forgotten
to initialise a variable before using it a manifest, or I've made a
small typo in a variable name resulting in the same thing.
Would it be possible to m
On 14/10/09 22:51, Luke Kanies wrote:
>
> I personally disagree that these idioms qualify as code smell, since I
> use them to avoid a warning (ruby -w is essentially entirely useless
> if you don't tend to use this idiom).
>
> I appear to be "unanimously" overridden, though, so I'll bow out
On 14/10/09 02:26, Ohad Levy wrote:
> You are describing something similar to the setup I have.
>
> If your problem is with variables, I would suggest to use external nodes
> or extlookup.
>
> maybe we can swtich this discussion back to puppet-users.
Ohad,
I'll ping you in #puppet to discuss.
On 14/10/09 00:38, Luke Kanies wrote:
>
> When you say 'override classes easily', what exactly do you mean? I
> think I'm especially confused by what you consider 'easily' vs. the
> other proposed solutions.
Ok, let me try and explain some more...
I've like to have a generic set of modules
On 19/04/09 03:06, Luke Kanies wrote:
>
> Sorry, I didn't make it clear in my original email, but the work I did
> fundamentally changes how modules search -- *all* files are searched
> through all module paths, rather than just the first found module.
>
I just raised #2716 [1] which fundam
19 matches
Mail list logo
