Repository navigation
feat: acquire Git credentials on demand using a detached broker - #60
Merged
Merged
Conversation
Replace guest credential seeding and refresh-credentials with private host-provider relay channels. Start an identity-checked broker on demand, detach its lifecycle, and retire it after idle demand expires. Include pinned static Linux helpers, reproducible build and release packaging, synthetic and detached coverage, lifecycle documentation, and archived credential specifications. Preserve unrelated local wiki changes outside this commit.
Refresh the README badge to the observed 1202 passing synthetic cases. Include the pending wiki notes on safe sparse-volume backups and private credential-directory repair.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
refresh-credentialscommand with automatic, on-demand host-provider acquisition over private exec/socket channels. Prepare or repair connections before lifecycle hooks and in-container cloning; retain destination authorization, rejection handling, and Azure URL/path behavior without guest token stores.Verification — previously executed, not rerun for this Git/PR operation
The archived execution record contains the reviewed evidence:
specs/changes/archive/20261022-git-broker-detached-lifecycle/tasks.md.git ls-remote, 8/8 credential gets, concurrent 8 gets + 4 Git operations in 1.838s; broker PID survived CLI exit. Stop plus idle exit completed in 5.642s total. Following an injected crash, 8.104s observation showed no automatic respawn; lookup missed as expected and the next start restored the connection. Reviewed cleanup confirmed plantsuite stopped, no remaining broker or LaunchAgent, restored files, unchanged credential-store metadata, and removal only of owned smoke artifacts; recovery backups preserved.Limits
swift build -c release --product adevcontainer; the pre-existing bare release build test-target issue is out of scope.No release/tag publication, merge, tap update, credential changes, or service installation is requested by this PR.