-
Notifications
You must be signed in to change notification settings - Fork 611
postgresql::server::config_entry should allow the empty string for value
parameter
#1602
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
Labels
Comments
antaflos
added a commit
to antaflos/puppet-postgresql
that referenced
this issue
Jul 5, 2024
PostgreSQL supports and allows config entries, such as those in postgresql.conf, to be set to the empty string. The `postgresql::server::config_entry` defined type, however, requires String[1] when supplying string values. This doesn't allow for the empty string. This change relaxes the allowed data types for the `value` parameter of `postgresql::server::config_entry` to `String` from `String[1]` and adds a spec test to support the change. Fixes puppetlabs#1602
3 tasks
antaflos
added a commit
to antaflos/puppet-postgresql
that referenced
this issue
Aug 14, 2024
PostgreSQL supports and allows config entries, such as those in postgresql.conf, to be set to the empty string. The `postgresql::server::config_entry` defined type, however, requires String[1] when supplying string values. This doesn't allow for the empty string. This change relaxes the allowed data types for the `value` parameter of `postgresql::server::config_entry` to `String` from `String[1]` and adds a spec test to support the change. Fixes puppetlabs#1602
antaflos
added a commit
to antaflos/puppet-postgresql
that referenced
this issue
Jan 20, 2025
PostgreSQL supports and allows config entries, such as those in postgresql.conf, to be set to the empty string. The `postgresql::server::config_entry` defined type, however, requires String[1] when supplying string values. This doesn't allow for the empty string. This change relaxes the allowed data types for the `value` parameter of `postgresql::server::config_entry` to `String` from `String[1]` and adds a spec test to support the change. Fixes puppetlabs#1602
antaflos
added a commit
to antaflos/puppet-postgresql
that referenced
this issue
Apr 22, 2025
PostgreSQL supports and allows config entries, such as those in postgresql.conf, to be set to the empty string. The `postgresql::server::config_entry` defined type, however, requires String[1] when supplying string values. This doesn't allow for the empty string. This change relaxes the allowed data types for the `value` parameter of `postgresql::server::config_entry` to `String` from `String[1]` and adds a spec test to support the change. Fixes puppetlabs#1602
antaflos
added a commit
to antaflos/puppet-postgresql
that referenced
this issue
Apr 22, 2025
PostgreSQL supports and allows config entries, such as those in postgresql.conf, to be set to the empty string. The `postgresql::server::config_entry` defined type, however, requires String[1] when supplying string values. This doesn't allow for the empty string. This change relaxes the allowed data types for the `value` parameter of `postgresql::server::config_entry` to `String` from `String[1]` and adds a spec test to support the change. Fixes puppetlabs#1602
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Bug
PostgreSQL supports and allows config entries, such as those in
postgresql.conf
, to be set to the empty string. Thepostgresql::server::config_entry
defined type, however, requiresString[1]
when supplying string values. This doesn't allow for the empty string.Expected Behavior
The
postgresql::server::config_entry
defined type should allow the empty string for itsvalue
parameter.Steps to Reproduce
A typical use case is setting database-specific parameters that can be empty:
This should render as follows in
postgresql.conf
, which is valid from PostgreSQL's PoV.However, the Puppet agent run fails with an error message:
This is because the empty string is not allowed here.
Environment
The text was updated successfully, but these errors were encountered: