docs(ziti): clarify private resource port mapping#153
Open
casey-brooks wants to merge 1 commit into
Open
Conversation
|
The latest Buf updates on your PR. Results from workflow buf-pr / buf (pull_request).
|
Contributor
Author
Test & lint summary
|
noa-lucent
approved these changes
Jun 13, 2026
noa-lucent
left a comment
There was a problem hiding this comment.
Reviewed the proto documentation-only change. The added comments clarify the positional multi-port mapping semantics without changing field numbers or generated API surface. I did not find any blocking issues.
Note: I could not rerun buf lint/buf breaking locally because buf is not installed in this environment.
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
host.v1andintercept.v1port mapping semantics for PrivateResource provisioning.Related to #154.
Tests / lint
buf lint— passed with no errors.buf breaking --against '.git#branch=main'— passed with no breaking changes.