Files
puppet-cloudkitty/manifests/db/postgresql.pp
Takashi Kajinami cf886d9814 Stop using absolute names for defined resource types
Since Puppet 4, names are always absolute. We already replaced usage of
absolute names for class inclusion, so can do the same for defined
resource types.

Change-Id: If817e99d795d120e0f1f4c9c7173f97b57b29255
2025-02-18 02:00:04 +09:00

50 lines
1.1 KiB
Puppet

# == Class: cloudkitty::db::postgresql
#
# Class that configures postgresql for cloudkitty
# Requires the Puppetlabs postgresql module.
#
# === Parameters
#
# [*password*]
# (Required) Password to connect to the database.
#
# [*dbname*]
# (Optional) Name of the database.
# Defaults to 'cloudkitty'.
#
# [*user*]
# (Optional) User to connect to the database.
# Defaults to 'cloudkitty'.
#
# [*encoding*]
# (Optional) The charset to use for the database.
# Default to undef.
#
# [*privileges*]
# (Optional) Privileges given to the database user.
# Default to 'ALL'
#
class cloudkitty::db::postgresql(
$password,
$dbname = 'cloudkitty',
$user = 'cloudkitty',
$encoding = undef,
$privileges = 'ALL',
) {
include cloudkitty::deps
openstacklib::db::postgresql { 'cloudkitty':
password => $password,
dbname => $dbname,
user => $user,
encoding => $encoding,
privileges => $privileges,
}
Anchor['cloudkitty::db::begin']
~> Class['cloudkitty::db::postgresql']
~> Anchor['cloudkitty::db::end']
}