Files
puppet-mistral/manifests/db/postgresql.pp
Takashi Kajinami d96d48c21f 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: Ic70ab3b52fe987189452b6068540e98e74861b41
2025-02-18 02:03:30 +09:00

49 lines
1.0 KiB
Puppet

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