theforeman / theforeman/foremanctl
Idea: use PgBouncer to handle PostgreSQL connections
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 27
- Forks
- 47
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 40
Description
If we use PgBouncer then we can separate the logic. Quoting https://www.pgbouncer.org/config.html#authentication-settings
PgBouncer handles its own client authentication and has its own database of users. These settings control this.
What this means is that we can our services (Candlepin, Foreman, Pulp) to connect to PgBouncer with fixed credentials. If you want to switch from a local to a remote database, we only need to reconfigure PgBouncer without touching the individual services.
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
No repository files, tests, or entry points are named. Start by reviewing the proposed PgBouncer authentication settings and how Candlepin, Foreman, and Pulp currently connect to PostgreSQL; done would require an agreed implementation plan for centralizing those credentials and supporting local or remote databases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100