[Puppet Users] Re: facter timeouts
On Tuesday, 5 November 2013 15:14:26 UTC, jcbollinger wrote: On Monday, November 4, 2013 10:38:00 AM UTC-6, james.e...@fasthosts.comwrote: Hi, I am having some issues with facter on a couple of servers which have a large number of ip addresses. Essentially, all my puppet runs time out because facter takes in excess of 25 seconds to populate the facts. Here is the list of interfaces - pretty much each one has an IP assigned. interfaces = eth0,eth1,eth1_1,eth1_2,eth1_3,eth1_4,eth1_5,eth1_6,eth1_7,eth1_8,eth1_9,eth1_10,eth1_11,eth1_12,eth1_13,eth1_14,eth1_15,eth1_16,eth1_17,eth1_18,eth1_19,eth1_20,eth1_21,eth1_22,eth1_23,eth1_24,eth1_25, eth1_26,eth1_27,eth1_28,eth1_29,eth1_30,eth1_31,eth1_32,eth1_33,eth1_34,eth1_35,eth1_36,eth1_37,eth1_38,eth1_39,eth1_40,eth1_41,eth1_42,eth1_43,eth1_44,eth1_45,eth1_46,eth1_47,eth1_48,eth1_49,eth1_50, eth1_51,eth1_52,eth1_53,eth1_54,eth1_55,eth1_56,eth1_57,eth1_58,eth1_59,eth1_60,eth1_61,eth1_62,eth1_63,eth1_64,eth1_65,eth1_66,eth1_67,eth1_68,eth1_69,eth1_70,eth1_71,eth1_72,eth1_73,eth1_74,eth1_75, eth1_76,eth1_77,eth1_78,eth1_79,eth1_80,eth1_81,eth1_82,eth1_83,eth1_84,eth1_85,eth1_86,eth1_87,eth1_88,eth1_89,eth1_90,eth1_91,eth1_92,eth1_93,eth1_94,eth1_95,eth1_96,eth1_97,eth1_98,eth1_99,eth1_100, eth1_101,eth1_102,eth1_103,eth1_104,eth1_105,eth1_106,eth1_107,eth1_108,eth1_109,eth1_110,eth1_111,eth1_112,eth1_113,eth1_114,eth1_115,eth1_116,eth1_117,eth1_118,eth1_119,eth1_120,eth1_121,eth1_122, eth1_123,eth1_124,eth1_125,eth1_126,eth1_127,eth1_128,eth1_129,eth1_130,eth1_131,eth1_132,eth1_133,eth1_134,eth1_135,eth1_136,eth1_137,eth1_138,eth1_139,eth1_140,eth1_141,eth1_142,eth1_143,eth1_144, eth1_145,eth1_146,eth1_147,eth1_148,eth1_149,eth1_150,eth1_151,eth1_152,eth1_153,eth1_154,eth1_155,eth1_156,eth1_157,eth1_158,eth1_159,eth1_160,eth1_161,eth1_162,eth1_163,eth1_164,eth1_165,eth1_166, eth1_167,eth1_168,eth1_169,eth1_170,eth1_171,eth1_172,eth1_173,eth1_174,eth1_175,eth1_176,eth1_177,eth1_178,eth1_179,eth1_180,eth1_181,eth1_182,eth1_183,eth1_184,eth1_185,eth1_186,eth1_187,eth1_188, eth1_189,eth1_190,eth1_191,eth1_192,eth1_193,eth1_194,eth1_195,eth1_196,eth1_197,eth1_198,eth1_199,eth1_200,eth1_201,eth1_202,eth1_203,eth1_204,eth1_205,eth1_206,eth1_207,eth1_208,eth1_209,eth1_210,eth1_211, eth1_212,eth1_213,eth1_214,eth1_215,eth1_216,eth1_217,eth1_218,eth1_219,eth1_220,eth1_221,eth1_222,eth1_223,eth1_224,eth1_225,eth1_226,eth1_227,eth1_228,eth1_229,eth1_230,eth1_231,eth1_232,eth1_233,eth1_234, eth1_235,eth1_236,eth1_237,eth1_238,eth1_239,eth1_240,eth1_241,eth1_242,eth1_243,eth1_244,eth1_245,eth1_246,eth1_247,eth1_248,eth1_249,eth1_250,eth1_251,eth1_252,eth1_253,eth1_254,eth1_255,eth1_256,eth1_257, eth1_258,eth1_259,eth1_260,eth1_261,eth1_262,eth1_263,eth1_264,eth1_265,eth1_266,eth1_267,eth1_268,eth1_269,eth1_270,eth1_271,eth1_272,eth1_273,eth1_274,eth1_275,eth1_276,eth1_277,eth1_278,eth1_279,eth1_280, eth1_281,eth1_282,eth1_283,eth1_284,eth1_285,eth1_286,eth1_287,eth1_288,eth1_289,eth1_290,eth1_291,eth1_292,eth1_293,eth1_294,eth1_295,eth1_296,eth1_297,eth1_298,eth1_299,eth1_300,eth1_301,eth1_302,eth1_303, eth1_304,eth1_305,eth1_306,eth1_307,eth1_308,eth1_309,eth1_310,eth1_311,eth1_312,eth1_313,eth1_314,eth1_315,eth1_316,eth1_317,eth1_318,eth1_319,eth1_320,eth1_321,eth1_322,eth1_323,eth1_324,eth1_325,eth1_326, eth1_327,eth1_328,eth1_329,eth1_330,eth1_331,eth1_332,eth1_333,eth1_334,eth1_335,eth1_336,eth1_337,eth1_338,eth1_339,eth1_340,eth1_341,eth1_342,eth1_343,eth1_344,eth1_345,eth1_346,eth1_347,eth1_348,eth1_349, eth1_350,eth1_351,eth1_352,eth1_353,eth1_354,eth1_355,eth1_356,eth1_357,eth1_358,eth1_359,eth1_360,eth1_361,eth1_362,eth1_363,eth1_364,eth1_365,eth1_366,eth1_367,eth1_368,eth1_369,eth1_370,eth1_371,eth1_372, eth1_373,eth1_374,eth1_375,eth1_376,eth1_377,eth1_378,eth1_379,eth1_380,eth1_381,eth1_382,eth1_383,eth1_384,eth1_385,eth1_386,eth1_387,eth1_388,eth1_389,eth1_390,eth1_391,eth1_392,eth1_393,eth1_394,eth1_395, eth1_396,eth1_397,eth1_398,eth1_399,eth1_400,eth1_401,eth1_402,eth1_403,eth1_404,eth1_405,eth1_406,eth1_407,eth1_408,eth1_409,eth1_410,eth1_411,eth1_412,eth1_413,eth1_414,eth1_415,eth1_416,eth1_417,eth1_418, eth1_419,eth1_420,eth1_421,eth1_422,eth1_423,eth1_424,eth1_425,eth1_426,eth1_427,eth1_428,eth1_429,eth1_430,eth1_431,eth1_432,eth1_433,eth1_434,eth1_435,eth1_436,eth1_437,eth1_438,eth1_439,eth1_440,eth1_441, eth1_442,eth1_443,eth1_444,eth1_445,eth1_446,eth1_447,eth1_448,eth1_449,eth1_450,eth1_451,eth1_452,eth1_453,eth1_454,eth1_455,eth1_456,eth1_457,eth1_458,eth1_459,eth1_460,eth1_461,eth1_462,eth1_463,eth1_464, eth1_465,eth1_466,eth1_467,eth1_468,eth1_469,eth1_470,eth1_471,eth1_472,eth1_473,eth1_474,eth1_475,eth1_476,eth1_477,eth1_478,eth1_479,eth1_480,eth1_481,eth1_482,eth1_483,eth1_484,eth1_485,eth1_486,eth1_487,
Re: [Puppet Users] Migrating from Puppet open-source to Puppet Enterprise
You definitely *can* move PuppetDB to another host, but I think you'd either be mostly on your own doing it, or need to reach out to support. AFAIK it's not supported by the installer, and I don't remember seeing documentation on it. The hardest part would probably be moving PuppetDB's database, but aside from that, it's really just a matter of telling the PE installer to put PuppetDB on the new host, and then changing some configuration files to point to the new host. If you happen to be building this out on VMs, I'd recommend splitting them from the start, and just adding resources as needed. But if you're looking to purchase PE, I imagine that puppet labs support would be able to give you some advice on this. -jantman On 11/07/2013 07:26 PM, Forrie wrote: We have perhaps 40 to 50 systems, give or take, that are mostly under Puppet management (not all). After having spent some time doing my own thing with open-source, I'm looking into migrating to PE. One question I have is relative to initial deployment -- if I decide to keep PuppetDB on the same server as Master, can I later migrate that role off onto another host?I don't believe we have enough traffic yet to justify breaking this all down (yet) -- and this will greatly simplify things. I also have the daunting task of re-writing all my individual manifests into proper modules :-) Thanks! -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/672ddcd1-19e4-4641-a27e-b5972e4c864d%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/527CD719.3020209%40jasonantman.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] require a defined type from another module
On Thursday, November 7, 2013 9:37:02 AM UTC-6, lth wrote:
Thanks but I still get a syntax error when doing
file{bar:
require = A:foo['baz']
}
Evidently you have not understood the advice for which you are giving
thanks, because it was to NOT DO THAT. Instead, do this:
file { 'bar':
# initial uppercase name components:
require = A::Foo['baz']
}
Note there that
1. EACH name component in a resource reference must be capitalized (i.e.
both the 'A' and the 'Foo'), and
2. the name component separator is a double colon (::), not a single
colon.
In addition, the actual names of modules, classes, and resource types
should begin with *lowercase* letters, so that resource references (which
use capital letters) are distinguished from other uses of class and
resource names. Thus, you should not have any module named A; rather, it
should be named a. Your definitions should thus have the form
# initial lowercase letters:
define a::foo(...) {
#...
}
The autoloader will expect to find that definition in module
path/a/manifests/foo.pp, where in principle case matters, but in practice
that depends on the filesystem.
John
--
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...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/ec36270d-cbc0-4653-ad71-7437795b9e7b%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Check the output of a exec
Hi all,
i'm making a manifest for an agent on windows.
I have to make some actions ONLY if a file already exists.
I tried in this way, but it seems dowsn't work..
class sql2008{
package { sql2008:
ensure = present,
}
exec {'check_dotnet':
command = 'IF EXIST
c:\Windows\Microsoft.NET\Framework\v4.0.30319\mscorlib.dll (echo 1) ELSE
(echo 0)',
returns = $check_dotnet_exist
}
notice( __ $check_dotnet_exist __ )
}
When i call the agent, the notice message is __ __
How can i save the output of the exec in a variable?
Ty all,
Giovanni
--
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...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/fbca5067-3eaf-46ed-8890-3e317a0a1b32%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Error: form() on Windows 2008 r2 Puppet agent
Hi josh
now i run the agent on a service and correctly works :-)
Il giorno giovedì 7 novembre 2013 16:10:51 UTC+1, Josh Cooper ha scritto:
On Thursday, November 7, 2013, giovanni possemato wrote:
Hi all,
i have recently installed puppet and this is my Scenario
Puppet master on ubuntu server 64 bit
Puppet client on Windows 2008 R2
I called my server on ubuntu using this command:
* puppet master --verbose --no-daemonize*
i call the agent on windows using this command:
*puppet agent --server {myserver.example.com
http://myserver.example.com} --waitforcert 10 --verbose --logdest
c:\puppet_agent.log*
But when the agent starts, it exit with this error:
*Error: Could not run: fork() function is unimplemented on this server*
I have installed my puppet server from scratch (it's a clean ubuntu
installation). using the instructions from the puppetlabs site:
$ wget http://apt.puppetlabs.com/puppetlabs-release-precise.deb $ sudo
dpkg -i puppetlabs-release-precise.deb $ sudo apt-get update
*The puppet master version is:*
root@mycomp:/# puppet master --version
3.3.1
*The ruby version on puppet master is:*
root@mycomp:/# ruby -v
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
*The puppet agent version is:*
c:\ProgramFiles ... puppet agent --version
3.3.1
*The ruby version on puppet agent is:*
c:\ProgramFiles ... ruby -v
ruby 1.9.3p448 2013-067-27 [i386-mingw32]
Anyone can help me to find the problem?
thank you all
Giovanni
--
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...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/db50b3a3-8c45-4cdf-b98c-d96067143ca5%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.
This is http://projects.puppetlabs.com/issues/21227
Josh
--
Josh Cooper
Developer, Puppet Labs
--
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...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/bc04ba22-918f-48ab-b386-bc9718991ce2%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Help with scaling puppetdb/postgres
On Thursday, November 7, 2013 6:53:25 PM UTC-6, David Mesler wrote: Well I found the cause of my 1% duplication rate. I was using the recommendation from this page ( http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML) to generate a facts.yaml file for mcollective. Most likely that would be because of the 'content' parameter of resource File['/etc/mcollective/facts.yaml']. The values of resource parameters are part of the catalog, so to the extent that nodes have different facts ($::hostname, for instance) their catalogs will differ. That seems to present a fundamental problem for scaling to large numbers of nodes when you're also using PuppetDB. I got rid of that and my catalog duplication went up to 73%. I'm not sure what else is changing, my catalogs are huge and I don't know how to diff unsorted json files. A quick and dirty way to compare would be simply to pass the catalogs through 'sort' before 'diff'ing them. Doing so will trash the json structure, but you should still get some useful information out of it. At minimum you will find out whether there are few or many differences between your catalogs, and you should get at least a general idea about what differs. This would be most effective if applied to catalogs that are distinct with the facts.yaml generation in place, but duplicate without. John -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/857f7988-2c26-49d5-a349-fbd57bb0f223%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] augeas onlyif problem
On 06/11/13 21:17, Jist Anidiot wrote:
I'm trying to make sure a specific user has a special ssh key used as
his identity file.
so I'm trying something like:
augeas{user_second_key:
context = /files/home/user/.ssh/config,
changes = [ ins IdentityFile after
/files/home/user/.ssh/config/IdentityFile[last()],
set /files/home/user/.ssh/config/IdentityFile[last()]
~/.ssh/user2nd_rsa,
],
onlyif = match /files/home/user/.ssh/config/IdentityFile
not_include ~/.ssh/user2nd_rsa,
}
However it adds the line every puppet run. I'm wondering what I might
be doing wrong.
Try:
onlyif = match
/files/home/user/.ssh/config/IdentityFile[.='~/.ssh/user2nd_rsa'] size == 0
--
Dominic Cleal
Red Hat Engineering
--
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...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/527D1DFF.60906%40redhat.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Catalogue graph building; nodes *then* edges?
Puppet 2.7 (primarily; soon going to 3). When a host's catalogue is built, Puppet collects all the graph nodes first, correct? And **then** adds the dependency edges between them? Why do I ask? Because I keep coming up against a desire for one class to know whether another one is in the catalogue before it declares a dependency relationship. defined() doesn't cut it, since the class in question may not have been scanned yet. If it's collect **then** connect, I'll be adding a FREQ for a function (or other means) to access/check the collection prior to the connexion phase.. -- Ken Coar Sanagendamgagwedweinini -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/1f1a037d-716b-4ffa-b4f0-1e0781190157%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Migrating from Puppet open-source to Puppet Enterprise
Thanks, Jason. I may toss the DB into a separate VM (the Master is on a real-iron system) just to be safe. As for the other roles, I think most of them can live happily on the Master with our smaller infrastructure. -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e8e8f9e7-6954-4e04-bf60-bfd9c3d86161%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Migrating from Puppet open-source to Puppet Enterprise
Puppet support engineer here. It would take some configuration tweaks to do the migration, but it should be doable. Once you're set up with a support plan, we can definitely assist you with that :) On Thursday, November 7, 2013 4:26:16 PM UTC-8, Forrie wrote: We have perhaps 40 to 50 systems, give or take, that are mostly under Puppet management (not all). After having spent some time doing my own thing with open-source, I'm looking into migrating to PE. One question I have is relative to initial deployment -- if I decide to keep PuppetDB on the same server as Master, can I later migrate that role off onto another host?I don't believe we have enough traffic yet to justify breaking this all down (yet) -- and this will greatly simplify things. I also have the daunting task of re-writing all my individual manifests into proper modules :-) Thanks! -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/c2e9177b-693a-42a8-a6eb-fdec46d9ffd9%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Catalogue graph building; nodes *then* edges?
Puppet 2.7 (primarily; soon going to 3). When a host's catalogue is built, Puppet collects all the graph nodes first, correct? And *then* adds the dependency edges between them? Why do I ask? Because I keep coming up against a desire for one class to know whether another one is in the catalogue before it declares a dependency relationship. defined() doesn't cut it, since the class in question may not have been scanned yet. If it's collect *then* connect, I'll be adding a FREQ for a function (or other means) to access/check the collection prior to the connexion phase.. -- Ken Coar Sanagendamgagwedweinini -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/527D2320.7000909%40gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Announce: Hiera 1.3.0-rc2 Available
**Release candidate**
Pre-release: Hiera 1.3.0 has not yet been released.
RC2: November 8, 2013 -- Reverted #18577
RC1: October 29, 2013 -- Problems came up functional-testing on ticket
#18577, which caused us to revert it, so this build never got pushed.
Hiera 1.3.0-rc2 Downloads
--
Source: https://downloads.puppetlabs.com/hiera/hiera-1.3.0-rc2.tar.gz
Available in native package format in the pre-release repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
For information on how to enable the Puppet Labs pre-release repos, see:
http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#enabling-the-prerelease-repos
Gems are available via rubygems at
https://rubygems.org/downloads/hiera-1.3.0.rc2.gem
or by using `gem install --pre hiera`
Mac packages are available at
https://downloads.puppetlabs.com/mac/hiera-1.3.0-rc2.dmg
Please report feedback via the Puppet Labs Redmine site, using an
affected hiera version of 1.3.0-rc2:
https://projects.puppetlabs.com/projects/hiera/
Hiera 1.3.0-RC2 release notes
---
New features
Most of the features contributed to Hiera 1.3 are intended to provide more
power by allowing new kinds of variable interpolation.
- Keys to YAML hashes can now contain interpolation syntax (#20220)
- You can now use `%{scope('variable_name')}` as a synonym for
`%{variable_name}` and `%{hiera('variable_name')}` to trigger a Hiera
lookup
from inside Hiera data. (We call this Hiera-ception) (#21367)
Feature #20220: Interpolate hash keys
Feature #20755: Add Pretty Print to command line hiera output
Feature #21367: Add support for a hiera variable syntax which interpolates
data by performing a hiera lookup
Better error handling and correctness fixes
---
There are also quite a few error handling changes, most of which had
previously
caused silent or unattributable error messages.
Bug #17094: hiera can end up in and endless loop with malformed lookup
variables
Bug #20519: small fix in hiera/filecache.rb
Bug #20645: syntax error cause nil
Bug #21669: Hiera.yaml will not interpolate variables if datadir is
specified as an array
Bug #22777: YAML and JSON backends swallow errors
Feature #21211: Hiera crashes with an unfriendly error if it doesn't have
permission to read a yaml file
Build/Packaging fixes and improvements
--
We are now building Hiera packages for Ubuntu Saucy, which previously was
unable to use Puppet because a matching Hiera package couldn't be built.
Older
Fedora 17 is no longer supported and hardcoded hostnames in
build_defaults.yaml
were removed.
Bug #22166: Remove hardcoded hostname dependencies
Bug #22239: Remove Fedora 17 from build_defaults.yaml
Bug #22905: Quilt not needed in debian packaging
Bug #22924: Update packaging workflow to use install.rb
Feature #14520: Hiera should have an install.rb
For the full list of closed issues specific to 3.3.1 see
http://projects.puppetlabs.com/versions/427.
Hiera 1.3.0-rc2 Contributors
--
Adrien Thebo, Andrew Parker, Bruno Léon, Eric Sorenson, Erik Dalén, Florian
Anderiasch, Gerardo Santana, Jeff McCune, Jesse Hathaway, Josh Partlow,
Matthaus Owens, Melissa Stone, Moses Mendoza, Scott Schneider, Stef T,
Thomas Hallgren, bob, nhuisman
Hiera 1.3.0-rc2 Changelog
Adrien Thebo (1):
41181fb Revert Merge pull request #137 from
lollipopman/add_hiera_lookup
Andrew Parker (5):
a1810b7 (#17094) Ensure that a leading $ resolves
6314cbb (Maint) Add heira to Gemfile so that you can run it
dbfedb4 (Maint) Clean up specs
8113855 (#22142) Ensure that :datadir is a String
d81a600 (#22777) Propagate errors from cached files
Bruno Léon (1):
e109ce8 Interpolate hash keys like already done for strings.
Eric Sorenson (1):
a749895 (#20519) Fix formatting typo in debug output
Erik Dalén (2):
3165eeb (#21211) Fix format string
6946bef (#21211) Raise a error on failed reading of cache
Florian Anderiasch (2):
d516dda Fixed configuration example consistency problem
c40ae07 And one more line inconsistent
Gerardo Santana (2):
dffb48d Fix for issue#20645
1ecd621 spec fix for for issue#20645
Jeff McCune (2):
8dd0a55 (maint) Fix gemspec version
e70c1c7 (maint) Fix gemspec version
Jesse Hathaway (11):
f62f660 Add support for a hiera variable syntax which interpolates
data by performing a hiera lookup
b39db81 Change hiera and scope lookup syntax to use a single sigil
for interpolation
6cd4845 Remove trailing whitespace in deep merge comment
981de92 Set backends to nil before loading a backend
1461832 Add support for a hiera variable syntax which interpolates
data by performing a hiera lookup:
4f683c4 Collapse
