feat: add provider-owned capability contracts#1013
Open
intel352 wants to merge 28 commits into
Open
Conversation
Register advertised resolvers with plugin process ownership so reload and shutdown cannot retain stale clients. Preserve compatibility fields and isolate provider requests and errors across the transport boundary.
Roll back server-loaded plugins rejected by the engine and swap prepared resolver registrations under one registry lock.
Treat repeated loads of one installed plugin as generations of a single resolver owner, and bind server plugin managers to engine lifecycle and admin routing.
Stage candidate resolver generations per application, drain in-flight calls before client shutdown, and close engines on every failed activation path.
Publish scoped replacements atomically, bound retirement by context, and defer candidate promotion until engine acceptance.
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
Why
Workflow is a framework, but core still owned concrete cloud behavior and its CI named specific provider repositories. This additive release creates the neutral contracts needed to move those lifecycles into canonical plugins before the v0.87 removal release.
Trust-only staging PRs #1011 and #1012 landed first so this PR cannot authorize its own workflow changes.
Public CI boundary
Validation
./scripts/test-check-public-workflow-policy.sh./scripts/check-public-workflow-policy.shactionlint .github/workflows/*.ymlshellcheckandbash -nfor contract-consumer scripts./.github/workflows/scripts/test-select-contract-consumers.shGOWORK=off go test -p=1 ./...GOWORK=off go test -race ./plugin/external/... -count=1GOWORK=off go test -race ./cmd/wfctl -run 'Provider|Credential|Registry|Kubernetes|Secret|Infra|Orphan|Contract' -count=1GOWORK=off go vet -p=1 ./...buf generatewith byte-identical generated outputgit range-diffconfirms all 28 reviewed patches are unchanged after rebasing onto ci: stage v0.86 workflow authority #1011/ci: stage v0.86 consumer authority #1012