Add customer-side proxy self-check - #289
Open
JayChung0258 wants to merge 1 commit into
Open
JayChung0258 wants to merge 1 commit into
JayChung0258 wants to merge 1 commit into
Conversation
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.
What changed
s2s-proxy validate --only proxyfor customer-side proxy pods.Scope
This check reads the customer-provided config and local pod state. It does not contact the customer Temporal cluster, Temporal Cloud, or the Kubernetes API. A successful result means the setup is internally consistent and possible to use. It does not verify customer-specific values against a separate specification.
Testing
make lintgo test -race -tags test_dep -count=1 ./app ./encryption ./preflightmake s2s-proxygit diff --check origin/main...HEAD