Skip to content

feat: adopt R1 MeshDB service identity - #488

Draft
cristibleotiu wants to merge 2 commits into
developfrom
feat/deeploy-0010-r1-meshdb-adoption-edge
Draft

feat: adopt R1 MeshDB service identity#488
cristibleotiu wants to merge 2 commits into
developfrom
feat/deeploy-0010-r1-meshdb-adoption-edge

Conversation

@cristibleotiu

@cristibleotiu cristibleotiu commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Problem

Deeploy must adopt the published R1 MeshDB service identity while remaining compatible with existing CockroachDB jobs and rejecting reserved database users before any billable or node-selection work.

Changes

  • Recognize the pinned R1 MeshDB image and retain legacy image compatibility.
  • Preserve secure CockroachDB input and update behavior.
  • Reject reserved users at request admission, before payment validation or node lookup.
  • Extend create, update, process-request, and verification coverage.

Verification

  • python -m unittest discover -s extensions/business/deeploy/tests -p 'test_*.py': 247 tests passed.
  • Exact edge commit 5c1adb53cd6e6dd457a950711247b8367962ac05 built and deployed in A6 run a6-7256936.
  • Three-host strict-500ms testbed passed all 10 gates: secure manager deployment, TLS contract, 10k-row replication, concurrent workloads, member outage/rejoin, sequential and fleet edge restarts, normal edit, and certificate regeneration.
  • A6 cleanup and retained-evidence scan passed with zero residual resources and zero secret violations.

Rollout

Land this edge change before, or atomically with, the coordinated dapp branding change. Do not deploy the dapp first.

Database release tested: ghcr.io/ratio1/r1-meshdb@sha256:3be00a63467628d0f5c3382be8ae7a885c5b658762dfd095fba0cb0b5549fab4.

Coordinated dapp PR: Ratio1/deeploy-dapp#143.

What changed:
- recognize exact R1 MeshDB and legacy image repositories
- reject reserved database users before certificate side effects
- pin the local verification bed to the signed digest and 500ms bound

Why:
- allow the final service image without changing persisted CockroachDB contracts
What changed:
- validate reserved CockroachDB users immediately after service-kind resolution
- cover create and update ordering before payment and node lookup

Why:
- prevent invalid managed-service requests from reaching downstream side effects
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant