hiera 2.0.0-x64-mingw32

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 316ccaf4e48cf2d8c30d8531d20a1155528e1aa0
+  data.tar.gz: fd038d50edc2f8c3dd6d21d21d30cc9463b11c4c
+SHA512:
+  metadata.gz: 2d9807317dd2ad62779fb8980f8d44075a7193d39b006209a5349095e4e5504563e01e056d48f296aabd3fef86422964b848ff1bcec3c8890756d143b031e347
+  data.tar.gz: 10d478df00b859bddf583631ae9fe9f2f1028b3394fda6dfd38d3e0a2a57ce32a1b41a681b814552594421d9b9b373b94c6300eccdd2291827abacf8f9c3a566

data/COPYING

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2010, 2011 R.I.Pienaar, Puppet Labs
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/LICENSE

@@ -0,0 +1,18 @@
+Puppet - Automating Configuration Management.
+
+Copyright (C) 2012-2014 Puppet Labs Inc
+
+Puppet Labs can be contacted at: info@puppetlabs.com
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+

data/README.md

@@ -0,0 +1,276 @@
+# Hiera
+
+[![Build Status](https://travis-ci.org/puppetlabs/hiera.png?branch=master)](https://travis-ci.org/puppetlabs/hiera)
+
+A simple pluggable Hierarchical Database.
+
+-
+**Tutorials:** Check the docs directory for tutorials.
+
+## Why?
+
+Hierarchical data is a good fit for the representation of infrastructure information.
+Consider the example of a typical company with 2 datacenters and on-site development,
+staging etc.
+
+All machines need:
+
+ - ntp servers
+ - sysadmin contacts
+
+By thinking about the data in a hierarchical manner you can resolve these to the most
+correct answer easily:
+
+<pre>
+     /------------- DC1 -------------\             /------------- DC2 -------------\
+    | ntpserver: ntp1.dc1.example.com |           | ntpserver: ntp1.dc2.example.com |
+    | sysadmin: dc1noc@example.com    |           |                                 |
+    | classes: users::dc1             |           | classes: users::dc2             |
+     \-------------------------------/             \-------------------------------/
+                                \                      /
+                                  \                  /
+                           /------------- COMMON -------------\
+                          | ntpserver: 1.pool.ntp.org          |
+                          | sysadmin: "sysadmin@%{domain}"     |
+                          | classes: users::common             |
+                           \----------------------------------/
+</pre>
+
+In this simple example machines in DC1 and DC2 have their own NTP servers, additionaly
+DC1 has its own sysadmin contact - perhaps because its a remote DR site - while DC2
+and all the other environments would revert to the common contact that would have the
+machines domain fact expanded into the result.
+
+The _classes_ variable can be searched using the array method which would build up a
+list of classes to include on a node based on the hierarchy.  Machines in DC1 would have
+the classes _users::common_ and _users::dc1_.
+
+The other environment like development and staging would all use the public NTP infrastructure.
+
+This is the data model that extlookup() have promoted in Puppet, Hiera has taken this
+data model and extracted it into a standalone project that is pluggable and have a few
+refinements over extlookup.
+
+## Enhancements over Extlookup
+
+Extlookup had just one backend, Hiera can be extended with your own backends and represent
+a few enhancements over the base Extlookup approach thanks to this.
+
+### Multiple backends are queried
+
+If you have a YAML and Puppet backend loaded and your users provide module defaults in the
+Puppet backend you can use your YAML data to override the Puppet data.  If the YAML doesnt
+provide an answer the Puppet backend will get an opportunity to provide an answer.
+
+### More scope based variable expansion
+
+Extlookup could parse data like %{foo} into a scope lookup for the variable foo.  Hiera
+retains this ability and any Arrays or Hashes will be recursively searched for all strings
+that will then be parsed.
+
+The datadir and defaults are now also subject to variable parsing based on scope.
+
+### No CSV support by default
+
+We have not at present provided a backward compatible CSV backend.  A converter to
+YAML or JSON should be written. When the CSV backend was first chosen for Puppet the
+Puppet language only supports strings and arrays of strings which mapped well to CSV.
+Puppet has become (a bit) better wrt data and can now handle hashes and arrays of hashes
+so it's a good time to retire the old data format.
+
+### Array Searches
+
+Hiera can search through all the tiers in a hierarchy and merge the result into a single
+array.  This is used in the hiera-puppet project to replace External Node Classifiers by
+creating a Hiera compatible include function.
+
+### Qualified Key Lookup
+You can use a qualified key to lookup a value that is contained inside a hash or array:
+
+<pre>
+$ hiera user
+{"name"=>"kim", "home"=>"/home/kim"}
+$ hiera user.name
+kim
+</pre>
+
+<pre>
+$ hiera ssh_users
+["root", "jeff", "gary", "hunter"]
+$ hiera ssh_users.0
+root
+</pre>
+
+## Future Enhancements
+
+ * More backends should be created
+ * A webservice that exposes the data
+ * Tools to help maintain the data files.  Ideally this would be Foreman and Dashboard
+   with their own backends
+
+## Installation
+
+Hiera is available as a Gem called _hiera_ and out of the box it comes with just a single
+YAML backend.
+
+Hiera is also available as a native package via apt (http://apt.puppetlabs.com) and yum (http://yum.puppetlabs.com). Instructions for adding these repositories can be found at http://docs.puppetlabs.com/guides/installation.html#debian-and-ubuntu and http://docs.puppetlabs.com/guides/installation.html#enterprise-linux respectively.
+
+At present JSON (github/ripienaar/hiera-json) and Puppet (hiera-puppet) backends are availble.
+
+## Configuration
+
+You can configure Hiera using a YAML file or by providing it Hash data in your code.  There
+isn't a default config path - the CLI script will probably assume _/etc/hiera.yaml_ though.
+The default data directory for file based storage is _/var/lib/hiera_.
+
+A sample configuration file can be seen here:
+
+<pre>
+---
+:backends:
+  - yaml
+  - puppet
+
+:logger: console
+
+:hierarchy:
+  - "sites/%{location}"
+  - common
+
+:yaml:
+   :datadir: /etc/puppetlabs/code/hieradata
+
+:puppet:
+   :datasource: data
+</pre>
+
+This configuration will require YAML files in  _/etc/puppetlabs/code/hieradata_ these need to contain
+Hash data, sample files matching the hierarchy described in the _Why?_ section are below:
+
+_/etc/puppetlabs/code/hieradata/sites/dc1.yaml_:
+<pre>
+---
+ntpserver: ntp1.dc1.example.com
+sysadmin: dc1noc@example.com
+</pre>
+
+_/etc/puppetlabs/code/hieradata/sites/dc2.yaml_:
+<pre>
+---
+ntpserver: ntp1.dc2.example.com
+</pre>
+
+_/etc/puppetlabs/code/hieradata/common.yaml_:
+<pre>
+---
+sysadmin: "sysadmin@%{domain}"
+ntpserver: 1.pool.ntp.org
+</pre>
+
+## Querying from CLI
+
+You can query your data from the CLI.  By default the CLI expects a config file in _/etc/hiera.yaml_
+but you can pass _--config_ to override that.
+
+This example searches Hiera for node data.  Scope is loaded from a Puppet created YAML facts
+store as found on your Puppet Masters.
+
+If no data is found and the facts had a location=dc1 fact the default would be _sites/dc1_
+
+<pre>
+$ hiera acme_version 'sites/%{location}' --yaml /opt/puppetlabs/puppet/cache/yaml/facts/example.com.yaml
+</pre>
+
+You can also supply extra facts on the CLI, assuming Puppet facts did not have a location fact:
+
+<pre>
+$ hiera acme_version 'sites/%{location}' location=dc1 --yaml /opt/puppetlabs/puppet/cache/yaml/facts/example.com.yaml
+</pre>
+
+Or if you use MCollective you can fetch the scope from a remote node's facts:
+
+<pre>
+$ hiera acme_version 'sites/%{location}' -m box.example.com
+</pre>
+
+You can also do array merge searches on the CLI:
+
+<pre>
+$ hiera -a classes location=dc1
+["users::common", "users::dc1"]
+</pre>
+
+## Querying from code
+
+This is the same query programatically as in the above CLI example:
+
+<pre>
+require 'rubygems'
+require 'hiera'
+require 'puppet'
+
+# load the facts for example.com
+scope = YAML.load_file("/opt/puppetlabs/puppet/cache/yaml/facts/example.com.yaml").values
+
+# create a new instance based on config file
+hiera = Hiera.new(:config => "/etc/puppetlabs/code/hiera.yaml")
+
+# resolve the 'acme_version' variable based on scope
+#
+# given a fact location=dc1 in the facts file this will default to a branch sites/dc1
+# and allow hierarchical overrides based on the hierarchy defined in the config file
+puts "ACME Software Version: %s" % [ hiera.lookup("acme_version", "sites/%{location}", scope) ]
+</pre>
+
+## Extending
+
+There exist 2 backends at present in addition to the bundled YAML one.
+
+### JSON
+
+This can be found on github under _ripienaar/hiera-json_.  This is a good example
+of file based backends as Hiera provides a number of helpers to make writing these
+trivial.
+
+### Puppet
+
+This is much more complex and queries the data from the running Puppet state, it's found
+on GitHub under _ripienaar/hiera-puppet_.
+
+This is a good example to learn how to map your internal program state into what Hiera
+wants as I needed to do with the Puppet Scope.
+
+It includes a Puppet Parser Function to query the data from within Puppet.
+
+When used in Puppet you'd expect Hiera to log using the Puppet infrastructure, this
+plugin includes a Puppet Logger plugin for Hiera that uses the normal Puppet logging
+methods for all logging.
+
+## License
+
+See LICENSE file.
+
+## Support
+
+Please log tickets and issues at our [JIRA tracker](http://tickets.puppetlabs.com).  A [mailing
+list](https://groups.google.com/forum/?fromgroups#!forum/puppet-users) is
+available for asking questions and getting help from others. In addition there
+is an active #puppet channel on Freenode.
+
+We use semantic version numbers for our releases, and recommend that users stay
+as up-to-date as possible by upgrading to patch releases and minor releases as
+they become available.
+
+Bugfixes and ongoing development will occur in minor releases for the current
+major version. Security fixes will be backported to a previous major version on
+a best-effort basis, until the previous major version is no longer maintained.
+
+
+For example: If a security vulnerability is discovered in Hiera 1.3.0, we
+would fix it in the 1 series, most likely as 1.3.1. Maintainers would then make
+a best effort to backport that fix onto the latest Hiera release they carry.
+
+Long-term support, including security patches and bug fixes, is available for
+commercial customers. Please see the following page for more details:
+
+[Puppet Enterprise Support Lifecycle](http://puppetlabs.com/misc/puppet-enterprise-lifecycle)