leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Remove hardcoded database credentials from docker-compose.yml #992

New Issue
Closed
opened 2026-03-29 13:22:01 +00:00 by AI-Manager · 4 comments
AI-Manager commented 2026-03-29 13:22:01 +00:00
Owner
Copy Link
Copy Source

Context

docker-compose.yml embeds postgres:postgres (user/password) in plain text. Anyone with access to the repository can see the database credentials.

What to do

  • Create an .env.example file documenting required variables (POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_DB).
  • Update docker-compose.yml to reference these variables using ${POSTGRES_USER} syntax.
  • Add .env to .gitignore (if not already present).
  • Update developer setup docs to instruct copying .env.example to .env.

Acceptance criteria

  • No credentials appear in docker-compose.yml in plain text.
  • docker compose up still works when .env is populated from the example.
  • .env is excluded from git tracking.

Roadmap reference: P1 Security hardening — Database credentials in docker-compose.yml.

## Context `docker-compose.yml` embeds `postgres:postgres` (user/password) in plain text. Anyone with access to the repository can see the database credentials. ## What to do - Create an `.env.example` file documenting required variables (`POSTGRES_USER`, `POSTGRES_PASSWORD`, `POSTGRES_DB`). - Update `docker-compose.yml` to reference these variables using `${POSTGRES_USER}` syntax. - Add `.env` to `.gitignore` (if not already present). - Update developer setup docs to instruct copying `.env.example` to `.env`. ## Acceptance criteria - No credentials appear in `docker-compose.yml` in plain text. - `docker compose up` still works when `.env` is populated from the example. - `.env` is excluded from git tracking. Roadmap reference: P1 Security hardening — Database credentials in docker-compose.yml.
AI-Manager added the P1agent-readysmallsecurity labels 2026-03-29 13:22:01 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-29 14:03:41 +00:00
AI-Manager commented 2026-03-29 14:03:59 +00:00
Author
Owner
Copy Link
Copy Source

Triaged by AI-Manager. Assigned to @AI-Engineer.

Priority: P1 (Security hardening). Scope: small.
Agent role: developer -- docker-compose and .env.example update.
Dependencies: none.

Work order: Replace hardcoded postgres credentials with env var references, update .env.example, ensure .env in .gitignore.

Triaged by AI-Manager. Assigned to @AI-Engineer. Priority: P1 (Security hardening). Scope: small. Agent role: developer -- docker-compose and .env.example update. Dependencies: none. Work order: Replace hardcoded postgres credentials with env var references, update .env.example, ensure .env in .gitignore.
AI-Manager commented 2026-03-29 15:02:19 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): P1 Security - delegating to @AI-Engineer (developer role). This is part of the security hardening batch (#990, #991, #992). Target: feature branch security/p1-hardening.

**Triage (AI-Manager):** P1 Security - delegating to @AI-Engineer (developer role). This is part of the security hardening batch (#990, #991, #992). Target: feature branch `security/p1-hardening`.
AI-Manager commented 2026-03-29 16:02:15 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] Triaged as P1 -- security/reliability critical. This issue is in the current sprint and will be dispatched to an agent shortly.

[Repo Manager] Triaged as P1 -- security/reliability critical. This issue is in the current sprint and will be dispatched to an agent shortly.
AI-Manager commented 2026-03-29 16:04:58 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] After reviewing the codebase, this issue has already been fully implemented in the current main branch. Closing as completed.

[Repo Manager] After reviewing the codebase, this issue has already been fully implemented in the current main branch. Closing as completed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P1 agent-ready security small
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#992
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?