feat: Add scoped peer deployment management - #218
Merged
Conversation
Connected servers can expose full deployment management without granting access to the host. Health checks now support separate protocols for each service.
nfebe
force-pushed
the
fix/peer-deployment-management
branch
from
August 23, 2026 13:26
c9dc799 to
262de97
Compare
Peer reads now require their module permission. Combined grants retain the highest deployment access.
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.
Allow connected servers to manage permitted deployments without granting host-wide access. Access combines module permissions, server-qualified deployment grants, API key scope, and peer policy.