Allow empty string value for config entries #1603
Open
+16
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
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 ofpostgresql::server::config_entry
toString
fromString[1]
and adds a spec test to support the change.Related Issues (if any)
#1602
Checklist
puppet apply
)