Forge Home

tinydata

pdk
Tiny Puppet Data

Example42

example42

47,039 downloads

465 latest version

4.3 quality score

Version information

  • 0.4.5 (latest)
  • 0.4.4
  • 0.4.3
  • 0.4.2
  • 0.4.1
  • 0.4.0
  • 0.3.3
  • 0.3.2
  • 0.3.1
  • 0.3.0
  • 0.2.7
  • 0.2.6
  • 0.2.5
  • 0.2.4
  • 0.2.3
  • 0.2.2
  • 0.2.1
  • 0.2.0
  • 0.1.12
  • 0.1.11
  • 0.1.10
  • 0.1.9
  • 0.1.8
  • 0.1.6
  • 0.1.5
  • 0.1.3
  • 0.1.2
  • 0.1.1
  • 0.0.25
  • 0.0.24
  • 0.0.23
  • 0.0.22
  • 0.0.21
  • 0.0.20
  • 0.0.19
  • 0.0.18
  • 0.0.17
  • 0.0.16
  • 0.0.15
  • 0.0.14
  • 0.0.13
  • 0.0.12
  • 0.0.11
  • 0.0.10
  • 0.0.8
  • 0.0.7
  • 0.0.6
  • 0.0.5
  • 0.0.4
  • 0.0.3
  • 0.0.2
  • 0.0.1
released Sep 4th 2018
This version is compatible with:
  • Puppet Enterprise >= 3.0.0 < 2016.4.0
  • Puppet >= 3.0.0 < 5.0.0
  • RedHat
    ,
    CentOS
    ,
    OracleLinux
    ,
    Scientific
    ,
    SLES
    ,
    Debian
    ,
    Ubuntu

Start using this module

Documentation

example42/tinydata — version 0.3.0 Sep 4th 2018

Tiny Data

This repository contains data used to manage applications on different Operating Systems.

It's currently used by the (Tiny Puppet module as default backend where is stored the application informations.

Update policy

Software evolves and things change. Our committment is to keep Tiny Data as updated as possible, so whenever new references to new vesions (for example in repos url) are available, they will be updated. If data for some Operating Systems is incorred (and it is) we will update it without caring about possible backwards incompatibilities on existing setups: the driving principle is to have the correct data for each version of each supported operating system and application.

We recommend to make a local fork of this module and update it from this upstream version only with extreme attention. Of course any bug reporting or pull request is welcomed.

Data structure

Each supported application has a sub directory in data/ which contains:

  • the hiera.yaml file which describes the hierarchy to use to lookup for the relevant application data.

  • the yaml files where data is stored according to the defined hierarchy.

A sample hiera.yaml is like this:

---
 :hierarchy:
   - "%{title}/osfamily/%{osfamily}"
   - "%{title}/default"
   - default

so the lookup is done, if $title == 'mariadb' and $::osfamily == 'RedHat' in these files:

tinydata/data/mariadb/osfamily/RedHat.yaml
tinydata/data/mariadb/default.yaml
tinydata/data/default.yaml

The last file contains general defaults for every application.