OK, if naming is going to get some discussion then we should probably start
a different thread as to not hijack this one.
I'll start that, please reply to the naming discussion at:
https://groups.google.com/forum/#!topic/puppet-dev/8j2IjZ1Ilog
Sorry for the temporary hijack.
-Jeff
--
You recei
This is just a continuation of a previous thread as to not hijack the
original discussion.
The question that needs a decision is, should post_resource_eval be renamed
given the context that it's currently implemented as a hook into the point
after all resources for a provider are evaluated and we
On Mar 6, 2014, at 21:27, Jeff McCune wrote:
On Thu, Mar 6, 2014 at 7:21 PM, Jeff McCune wrote:
> If so, is it worth renaming it sooner rather than later?
>
Or is it worth renaming at all? I didn't mean to assume that part.
Yeah, agree with renaming it. I have some horrible monkey patch that
On Thu, Mar 6, 2014 at 7:21 PM, Jeff McCune wrote:
> If so, is it worth renaming it sooner rather than later?
>
Or is it worth renaming at all? I didn't mean to assume that part.
-Jeff
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To
On Thu, Mar 6, 2014 at 11:23 AM, Stefan Schulte <
stefan.schu...@taunusstein.net> wrote:
> Hi Erik,
>
> On 06.03.2014 09:28, Erik Dalén wrote:
> > Isn't this what was done in http://projects.puppetlabs.com/issues/3946 ?
> > So should be available in 3.4.0+
> >
> > Was discussed in this mail
> > th
+1 to this idea from Eric.
However, be VERY careful that you don't end up stepping on data across
runs. You'll need to clear that variable at each start and, if you use a
class variable, you'll need to make sure that they're all unique across ALL
types.
Trevor
On Thu, Mar 6, 2014 at 5:59 PM, ba
Sorry about the delay in getting this out.
Joined:
Errrpeople. I forgot to write this down at the time.
Puppet:
Held over2200: Solaris versions with timestamps. Contributor supplied
solaris packages to repro. In our backlog to fix ourselves. 3.6. Closing
because it isn't making any progress
Not sure if this will work as expected for your custom type, but a thought
might be to set some (provider) class variable in #flush and then, in
::post_resource_eval, check if this variable is set and do the restart (so
each flush does no actual work other than setting the flag).
Eric
On Thurs
I've posted this to Puppet-Users to better ensure those publishing to the
Puppet Forge see it. If you want to reply, please reply to Puppet-Dev.
With the launch of Puppet Enterprise 3.2 this week, the Puppet Forge added
search filters to help people find modules that are compatible with their
Pupp
> To bring this back to mysql I guess I'd see:
> mysql-provider
> mysql-server
> mysql-server-accounts
> mysql-server-backup
> mysql-client
Do we have a precedent for these kinds of patterns?
--
Igor Galić
Tel: +43 (0) 664 886 22 883
Mail: i.ga...@brainsware.org
URL: http://brainsware.org/
On Wednesday, March 5, 2014 11:56:08 AM UTC-6, Shook Shivers wrote:
>
> I get Error: Could not prefetch zenoss_device provider 'zenoss_device':
> undefined local variable or method `resource' for
> Puppet::Type::Zenoss_device::ProviderZenoss_device:Class when using the
> following
>
> def sel
Hi Erik,
On 06.03.2014 09:28, Erik Dalén wrote:
> Isn't this what was done in http://projects.puppetlabs.com/issues/3946 ?
> So should be available in 3.4.0+
>
> Was discussed in this mail
> thread: https://groups.google.com/forum/#!topic/puppet-dev/Iqs5jEGfu_0
thanks for finding the ticket and
Isn't this what was done in http://projects.puppetlabs.com/issues/3946 ?
So should be available in 3.4.0+
Was discussed in this mail thread:
https://groups.google.com/forum/#!topic/puppet-dev/Iqs5jEGfu_0
On 6 March 2014 00:54, Stefan Schulte wrote:
> Hello,
>
> is there a way for a custom provi
13 matches
Mail list logo
