fix(sdk): require Platform identity for production Solutions - #1058
Merged
Merged
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
1 participant
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
/healthand/readyavailable to Kubernetes probes.Security impact
Previously, requests that reached the Compute gateway could bypass the Platform’s organization-role checks and be handled anonymously by a Solution. This closes that path in new production Solution images.
Verification
cd sdk && uv run --locked --group dev pytest -q(268 passed)cd sdk && uv run --locked ruff check .cd sdk && uv run --locked --group dev ty checkDeployment
Existing Solution images contain the old SDK and must be rebuilt and redeployed. This PR does not change the running production images or the Compute release pointer.