/[adm]/puppet/modules/puppet/manifests/stored_config.pp
ViewVC logotype

Contents of /puppet/modules/puppet/manifests/stored_config.pp

Parent Directory Parent Directory | Revision Log Revision Log


Revision 2395 - (show annotations) (download)
Fri Feb 10 19:05:33 2012 UTC (9 years, 7 months ago) by misc
File size: 1040 byte(s)
split stored_config in a separate class, and refactor the configuration.
This will ease a switch to postgresql once I found how to solve the
issues of bootstrapping it ( for automated reinstallation )
1 class puppet::stored_config {
2 # TODO uncomment when the following problem have been fixed
3 # - how to bootstrap the installation of the infrastructure ( since we use
4 # stored_config for postgresql::remote_db_and_user, we need to have a sqlite3
5 # database first and then declare the database, and then switch to it )
6 # - how do we decide when we get sqlite3 ( for small test servers ) and
7 # when do we decide to get the real pgsql server ( for production setup )
8 #
9 # if ($::environment == 'production') {
10 # # FIXME not really elegant, but we do not have much choice
11 # # this make servers not bootstrapable for now
12 # $pgsql_password = extlookup('puppet_pgsql','x')
13 #
14 # postgresql::remote_db_and_user { 'bugs':
15 # description => 'Puppet database',
16 # password => $pgsql_password,
17 # }
18 #
19 # $database = 'pg'
20 # } else {
21 $database = 'sqlite3'
22 # }
23 #
24 package { ["ruby-$database", 'ruby-rails']: }
25
26 $db_config = template('puppet/db_config.pp')
27 }

  ViewVC Help
Powered by ViewVC 1.1.28