| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
The new implementation of calling_module turned out to be the same as
puppet's own module_name. This makes it simply and alias so that we keep
that as the definition of calling_module.
|
|
|
|
The initial fix for looked up values downcased everything that was being
returned. This causes problems when the data is not a string that the
previous behavior was to only do this for the calling_class and
calling_module. This commit us returns to that behavior.
|
|
The nested definition of the recurse_for_hostclass method caused that
method to be created lazily and as a public method. By pulling it out to
be declared outside the calling method it can be made private and
created only once. It has also been renamed to show the intention
instead of the mechanism (recursion).
|
|
|
|
|
|
|
|
Puppet no longer returns :undefined as a special value from variable
lookups. This commit removes this extra check from the Hiera puppet
backend.
|
|
Previously the Hiera::Backend::Puppet_backend code assumed that
Hiera::Backend had already been included. This was not true, at least in
the tests. This commit has the backend require the files that it expects
to already be loaded for it to work correctly.
|
|
Consider:
````
class foomodule::params {
$myitem = false
...
````
The current code won't handle this because `if temp_answer` is the same
as `if false`.
This commit changes it to use `temp_anser.nil?` instead.
|
|
The hiera puppet backend called the include function without passing the
argument as an array. This changes it to call the function correctly.
|
|
The hiera-puppet code base now uses two space indentation. This patch
also removes unnecessary calls to `Hiera::Scope`, which is no longer
required because core Puppet's scope object allows variable lookup via
the `[]` method.
This commit includes updated specs.
|
|
Synchronize with the way backends work in Hiera 1.0 by starting with nil
instead of Backend.empty_answer
|
|
Puppet support hashes, so hiera-puppet backend should also support hash
values.
|
|
evaluated in scope
|
|
|
|
|
|
Fix some unfriendly behavior wrt class names that don't resolve using scope
|
|
|
|
|
|
|
|
|
|
|
|
|
