-
Notifications
You must be signed in to change notification settings - Fork 611
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
postgresql::server::extension needs to have defaults for postgresql_psql #582
postgresql::server::extension needs to have defaults for postgresql_psql #582
Conversation
that.. makes sense. |
psql_group => $group, | ||
psql_path => $psql_path, | ||
port => $port, | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you fix the indentation to 2 spaces?
@igalic it looks like manifests/server/initdb.pp uses postgresql_psql, but doesn't have a Postgresql_psql setting any defaults. I could do the same over there, as with the extension, but the question is whether a postgresql::server class is active too at the same time |
this almost sounds like it's a call for… ACCEPTANCE TESTS! |
Can't imagine that changes spaces in 6d937f0 broke the build :( |
these are the failures as reported by travis |
you might have to rebase, post #584 |
@igalic thx for the pointer! btw, do you want to have the manifests/server/initdb.pp case addressed too in the same pull request? |
if it's not too much effort for you: sure! also, once done you may wanna clean up these commits by squashing them down to a single one (or… few:) |
i just noticed your rebase is actually a merge commit, please take a look at this |
Using same pattern as with postgresql::server::database. observed when installing the pg_trgm using pgsql 9.4
…ql_psql-fix postgresql::server::extension needs to have defaults for postgresql_psql
…n-postgresql_psql-fix postgresql::server::extension needs to have defaults for postgresql_psql
Using same pattern as with postgresql::server::database.
observed when installing the pg_trgm using pgsql 9.4 for puppetdb
affects: puppetlabs-postgresql 4.2.0
code used:
class { 'postgresql::globals':
manage_package_repo => true,
version => $postgres_version,
}->
class { 'postgresql::server':
listen_addresses => '*',
}->
class { '::puppetdb::database::postgresql':
manage_server => false,
database_name => $database_name,
database_username => $database_username,
database_password => $database_password,
before => [Class['puppetdb::server'],
Class['puppetdb::server::validate_db']],
}
class { 'postgresql::server::contrib':
}->
postgresql::server::extension { 'pg_trgm':
database => $database_name,
}
class { '::puppetdb::server':
listen_address => '0.0.0.0',
listen_port => '8080',
ssl_listen_address => '0.0.0.0',
ssl_listen_port => '8081',
open_ssl_listen_port => true,
database => 'postgres',
}