-
Notifications
You must be signed in to change notification settings - Fork 613
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
Do not add version component to repo definition #1282
Conversation
postgresql::repo::apt_postgresql_org is a classthat may have no external impact to Forge modules. This module is declared in 70 of 576 indexed public
|
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.
https://wiki.postgresql.org/wiki/Apt tells me this isn't just for Ubuntu but just apt.postgresql.org in general so 👍 from me.
I've allowed it to run the tests so we'll see what they say when they complete or if you need to You may need to modify some tests. At least the style guide says to use single quotes for strings without variables (and I think puppet-lint also enforces this).
|
@weastur Apologies for the wait but everything is looking good to me so I'm gonna go ahead and merge. Thanks for putting in the work and I look forward to seeing more from you in the future |
Do not add version component to repo definition
According to the official documentation there is no need to add version component to repository line.
There are no predefined list of allowed components names, but some tools, like
command-not-found, manage they own list and do not expect to meet something like13in component name. Source code here This causes exception like this whileapt updateStrictly speaking this is not the direct problem of this module, but my suggestion is to align behaviour of puppet module with official PostgreSQL documentation.