DevOps: Cloud Agent native Postgres bootstrap (#287) #420
No reviewers
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:open_issues
agents
agent:security_audit
agent:verify
area
timecurve
arena
arena-v2
audit
block:feature_review
block:security
bug
contracts
design
devops
docs
documentation
enhancement
epic
feature
frontend
indexer
low priority
megaeth
operations
ops
performance
QA
qa checklist
referrals
removal
security
smart-contracts
tech-debt
testing
time-arena
timecurve
visual-qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
code/yieldomega!420
Loading…
Reference in a new issue
No description provided.
Delete branch "cursor/cloud-agent-postgres-native-b8a5"
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?
Summary
Closes #287.
Cloud Agents consistently hit Postgres failures when Docker
yieldomega-pgis unavailable. This MR adds an idempotent native PostgreSQL 16 bootstrap path on port 5433 withpostgresql-client,yieldomegarole (CREATEDB), and smoke verification—wired into Cloud bootstrap,AGENTS.md, and invariants.Rebased onto
main(merged guardrails §13 with #289 DeployDev scope + #287 native Postgres).Changes
scripts/bootstrap-cloud-postgres-native.sh— install/configure Postgres 16 on:5433, role + databasesscripts/verify-cloud-postgres.sh—psql,pg_isready,SELECT 1, CREATEDB probebootstrap-cloud-vm-toolchain.sh+.cursor/environment.json— invoke native bootstrapverify-cloud-vm-toolchain.sh— Postgres verify row; Docker SKIP when daemon unavailableAGENTS.md, invariants (INV-CLOUD-287-*), guardrails skill, qa-local-full-stackAcceptance checklist
psqlexists;SELECT 1onDATABASE_URLafter bootstrap (no Docker)bash scripts/bootstrap-cloud-postgres-native.shthenbash scripts/verify-cloud-postgres.shyieldomegacan drop/recreate DB viapsql(CREATEDB)verify-cloud-postgres.shCREATEDB probebash scripts/verify-podium-live-anvil.shbash scripts/bootstrap-cloud-postgres-native.sh×2AGENTS.md+.cursor/environment.jsonreference automated pathBlockers: none
Third-party verification
Closes #287 when merged.
Security review (automated)
Commit reviewed:
4740bda2be9182af6c116f67ebc99a942a571856Scope: Added/modified Cloud Agent dev tooling only —
scripts/bootstrap-cloud-postgres-native.sh,scripts/verify-cloud-postgres.sh, wiring inbootstrap-cloud-vm-toolchain.sh/verify-cloud-vm-toolchain.sh,.cursor/environment.json, and related docs/invariants. No indexer API, frontend, or contract runtime changes.Method: MR diff review; traced env/config inputs to sinks (shell
sed,psql, role/database DDL); compared to existing local Docker Postgres path (yieldomega-pgwith--network host, sameyieldomega/passwordon port 5433).Outcome: FINDINGS: 0 (no medium, high, or critical issues on this diff).
Notes (below reporting threshold):
CREATEDBmatch pre-existing local QA conventions;DATABASE_URLtargets127.0.0.1and bootstrap does not widenlisten_addresses/pg_hba.confbeyond distro defaults (native path is not broader than the existing Docker host-network setup).PG_HOST_PORT/ cluster env vars are operator-controlled bootstrap inputs on ephemeral Cloud VMs; no attacker-controlled path from production surfaces.Inline threads: none (no findings to anchor).
Cursor automation — MR security review
changed the description
added 7 commits
main34408980- feat(devops): native Postgres bootstrap for Cloud Agents (#287)Compare with previous version
Security review (automated)
Commit reviewed:
34408980eee16d64527c303880d65d73c7c7ab16Scope: Re-review after rebase onto
main. Added/modified Cloud Agent dev tooling only —scripts/bootstrap-cloud-postgres-native.sh,scripts/verify-cloud-postgres.sh, wiring inbootstrap-cloud-vm-toolchain.sh/verify-cloud-vm-toolchain.sh,.cursor/environment.json, and related docs/invariants. No indexer HTTP API, frontend, or contract runtime changes.Method: MR diff review (vs
0b2cbc0220a156d8d62bdf4e1eb2d9f198bef329); traced env/config inputs (PG_HOST_PORT,PG_HOST,DATABASE_URL,YIELDOMEGA_PG_VERSION) to sinks (sed,psql, role/database DDL); compared to existing Dockeryieldomega-pgpath (--network host, sameyieldomega/passwordon port 5433).Outcome: FINDINGS: 0 (no medium, high, or critical issues on this diff).
Prior review: Commit
4740bda2had the same outcome; rebase did not introduce new attacker-controlled surfaces or widen network/auth boundaries beyond that review.Notes (below reporting threshold):
CREATEDBmatch pre-existing local QA conventions;DATABASE_URLdefaults to127.0.0.1and bootstrap does not modifylisten_addresses/pg_hba.conf(native path is not broader than the documented Docker host-network setup).PG_HOST_PORT/ cluster env vars are operator-controlled bootstrap inputs on ephemeral Cloud VMs; no path from production user input to these sinks.DATABASE_URL(includes dev password) to stdout — acceptable for local-only credentials already documented inAGENTS.md.Inline threads: none (no findings to anchor).
Cursor automation — MR security review
mentioned in commit
c6820b64aamentioned in merge request !421
mentioned in commit
4cb4750028