Takashi Kajinami 6976d5b26a 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: I514eeabebd81012d07bc87f00b454b3252fb42f9
2025-02-18 02:06:12 +09:00

50 lines
1.0 KiB
Puppet

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