puppetlabs / puppetlabs/puppetlabs-postgresql
Handle multiple postgresql versions with instances
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 232
- Forks
- 610
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 4
Description
This issue is a follow up of PR #1450.
@bzed mentioned that it might be beneficial to add the version to the instance name. this would allow the user to have instances of the same name with different versions. A good example is an upgrade to a newer version.
Possible pitfalls:
- package management
- dependency to postgresql::server for defaults
- postgresql::globals expects a single string for $version
might be a good preparation for #1524
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading PR #1450 and the related discussion, then inspect how instance names, versions, package management, postgresql::server defaults, and postgresql::globals are handled. Done means the module can manage same-named instances on different PostgreSQL versions without breaking those dependencies; consider how this prepares for #1524.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, ruby
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100