Skip to content

feat: optional trust registry - #93

Closed
vthwang wants to merge 7 commits into
mainfrom
feat/optional-trust-registry
Closed

vthwang wants to merge 7 commits into
mainfrom
feat/optional-trust-registry

Conversation

@vthwang

@vthwang vthwang commented Oct 24, 2026

Copy link
Copy Markdown
Member

No description provided.

vthwang and others added 7 commits October 20, 2026 18:15
Define in-place enablement so existing full stacks can add a registry without rebuilding.

Cover configuration, identity, Vault, recovery, and acceptance requirements.

Signed-off-by: vthwang <vthwang.work@gmail.com>
Enable dedicated registries on new and existing stacks while preserving community data.

- Persist enablement state and deliver scoped credentials through Vault
- Merge VTC configuration and publish signed Registry referrals
- Integrate upgrades, resources, teardown, and failed Job cleanup

Native hosted DID provisioning remains blocked by the upstream VTA CLI signer issue.

Signed-off-by: vthwang <vthwang.work@gmail.com>
Avoid the migration 44 collision introduced by main.

- Merge current main fixes and dependency updates.
- Renumber Trust Registry migrations to 45.
- Verify resource defaults with the full schema and Trust Registry settings.

Signed-off-by: vthwang <vthwang.work@gmail.com>
Prepare Registry identities before VTC creation and preserve resumable setup receipts.

- replace Vault-delivered bootstrap credentials with the Registry headless setup flow
- surface sanitized Job logs and retain recovery receipts
- pass the Registry DID through new Full Stack VTC setup

Signed-off-by: vthwang <vthwang.work@gmail.com>
Signed-off-by: Geoff Turk <geoff@ic3.dev>
Signed-off-by: vthwang <vthwang.work@gmail.com>
Co-authored-by: vthwang <vthwang.work@gmail.com>
Cancel Registry workers before acquiring the teardown lease and clear abandoned Registry maintenance leases under the advisory lock. Apply the protocol to owner, admin, pool, and load-test cleanup paths.

Signed-off-by: vthwang <vthwang.work@gmail.com>
Prevent an opted-in new stack from being reported as running after Registry setup fails.

Persist the Registry failure as the session error, pin it to the Registry phase, and document and test the behavior.

Signed-off-by: vthwang <vthwang.work@gmail.com>
@vthwang vthwang self-assigned this Oct 24, 2026
@vthwang vthwang added the enhancement New feature or request label Oct 24, 2026
@vthwang vthwang closed this Oct 24, 2026
@vthwang
vthwang deleted the feat/optional-trust-registry branch October 24, 2026 08:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants