leap_platform.git/puppet/modules/site_config, branch 0.3.0rc3

fix name of base class file

2013-10-03T19:27:33+00:00

Change-Id: I844970f1c8f895d5a460d5082bfa1a2a88b32ecd

create a site_config::packages directory, move site_config::base_packages to site_config::packages::base

2013-09-26T19:47:03+00:00

add site_config::packages::gnutls for inclusion (#3955)

Change-Id: I9599eb26844503613c16f57ee17d6ea7bd0cf6fb

added site_config::x509::client_ca::cert and site_config::x509::client_ca::key for client_ca deployment (#3917)

2013-09-24T19:03:36+00:00

move commercial x509 deployment to site_x509 (Feature #3889)

2013-09-24T08:06:22+00:00

seperate cert and key deployment (#3918)

2013-09-24T07:20:42+00:00

Merge branch 'feature/3782_Discuss_run_stages_on_deploy' into develop

2013-09-20T17:08:40+00:00

move all resources that are applied on every node into site_config::default (#3782)

2013-09-20T17:02:02+00:00

in commit 338833, we established a relationship between all
resources that have a leap_service tag, that are called in site.pp.
But we had some resources as default on every node in site.pp
(apt::update, Package { require => Exec['apt_updated'] },
site_config::slow and stdlib), that were still lacking any
relationship to the leap_service tag.
By moving them into default.pp they automatically are executed
before resources with a leap_service tag.

webapp: Depend services on deployment of default key, cert and ca (Feature #3838)

2013-09-19T11:11:24+00:00

tidy openvpn x509 definitions (#3831)

2013-09-19T10:29:15+00:00

only deploy x509 stuff for nodes if it existes in hiera (Feature #3875)

2013-09-19T10:19:00+00:00