On 04/09/14 01:50, Matthaus Owens wrote:
Dominic,
Facter master just passed acceptance with trusty, so it is now
available in the nightly repos.
Great, thanks. Looks like it got further, but failed on an obscure
issue between the Foreman API and one of our types/providers.
--
Dominic Cleal
2) Why would allowing one or both of the Bigs prevent Number from being
allowed as a serializable type?
Not sure I said that. The problem is that if something is potentially
Big... then a database must be prepared to deal with it and it has a
high cost.
Every Puppet value is
I have some code that's doing module searching in the module path:
example = Puppet::Module.find('example', Puppet[:environment].to_s)
raise(LoadError, Unable to find example module in modulepath
#{Puppet[:modulepath]}) unless example
In Puppet 3.6, the second line is triggering a the
I think it's Puppet[:basemodulepath] but this needs to be combined with
your environment path search.
Trevor
On Thu, Sep 4, 2014 at 1:03 PM, Nan Liu nan@gmail.com wrote:
I have some code that's doing module searching in the module path:
example = Puppet::Module.find('example',
On 2014-04-09 16:40, Ken Barber wrote:
2) Why would allowing one or both of the Bigs prevent Number from being
allowed as a serializable type?
Not sure I said that. The problem is that if something is potentially
Big... then a database must be prepared to deal with it and it has a
high cost.
So right now, we have alternating native postgresql columns for the
bare types: text, biginteger, boolean, double precision. This provides
us with the ability to use the most optimal index for the type, and of
course avoid storing any more then we need to. As I mentioned at the
top of the
I would think if we had transport encoding issues (like mspack not
supporting a larger type natively) we could decode before we store I
guess. Thats an alternative. It means traversing the tree to find
these cases and modifying them on the float perhaps. Things like
zipper in clojure make
Hi Nan,
The modulepath is really only meaningful from an actual environment
instance. What code are you writing? You'll probably want to lookup the
current environment or make use of the environment instance available in
your local context (if there is one).
On Thu, Sep 4, 2014 at 10:08 AM,
On Thursday, September 4, 2014 9:40:43 AM UTC-5, Ken Barber wrote:
Every Puppet value is potentially a Big now. What new cost is involved?
I'm having trouble seeing how a database can deal efficiently with
Puppet's
current implicit typing anyway, Big values notwithstanding.
Puppet 3.7.0 is a backward-compatible features and fixes release in the Puppet
3 series. The biggest things in this release are:
* A nearly-final implementation of the Puppet 4 language
* Preview support for a new, fast, natively compiled Facter
* 64-bit Puppet packages
Thanks, Ken. Could you devote a few words to how PuppetDB chooses which of
those alternative columns to use for any particular value, and how it
afterward tracks which one has been used?
So PuppetDB, in particular fact-contents, and the way it stores leaf
values makes a decision using a very
Yes, I'm looking for the environment specific modulepath.
Maybe this is a more complete example:
example = Puppet::Module.find('example', Puppet[:environment].to_s)
raise(LoadError, Unable to find example module in modulepath
#{Puppet[:modulepath]}) unless example
On Thu, Sep 4, 2014 at 12:34 PM, Nan Liu nan@gmail.com wrote:
Yes, I'm looking for the environment specific modulepath.
Maybe this is a more complete example:
example = Puppet::Module.find('example', Puppet[:environment].to_s)
raise(LoadError, Unable to find example module in modulepath
On Thu, Sep 4, 2014 at 1:05 PM, Joshua Partlow
joshua.part...@puppetlabs.com wrote:
On Thu, Sep 4, 2014 at 12:34 PM, Nan Liu nan@gmail.com wrote:
Yes, I'm looking for the environment specific modulepath.
Maybe this is a more complete example:
example = Puppet::Module.find('example',
On Thu, Sep 4, 2014 at 1:14 PM, Andy Parker a...@puppetlabs.com wrote:
On Thu, Sep 4, 2014 at 1:05 PM, Joshua Partlow
joshua.part...@puppetlabs.com wrote:
On Thu, Sep 4, 2014 at 12:34 PM, Nan Liu nan@gmail.com wrote:
Yes, I'm looking for the environment specific modulepath.
Maybe
Earlier, we had a discussion about the syntax of the resource
expression. As a result of that, we decided to do a user UX study
to help us guide the decision.
We did get the results of the UX research just in time to make a
decision and do the required corrections for the 3.7.0. The meeting
For the past couple of months we've had a puppet-4 branch running which
allowed us to land any breaking changes that should go into puppet 4.0
without having to hold onto them. Now that puppet 3.7.0 has been released,
that opens up the master branch for puppet 4.0 development! Rejoice!
Over the
17 matches
Mail list logo
