[REV-2383] Scope integrations and provider setup by team - #15816
Open
warp-agent-staging[bot] wants to merge 4 commits into
Open
[REV-2383] Scope integrations and provider setup by team#15816warp-agent-staging[bot] wants to merge 4 commits into
warp-agent-staging[bot] wants to merge 4 commits into
Conversation
Contributor
Author
|
This PR was generated with Warp. Comment    |
…ev-2383-integrations-provider # Conflicts: # crates/warp_server_client/src/graphql_helpers.rs # crates/warp_server_client/src/graphql_helpers_tests.rs
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.
Description
Scope
oz integration list, create, update, andoz provider setupto the selected team. Integration requests carry approvedRequestTeamScopeproof through OAuth retries and add the raw team UID only at the GraphQL transport boundary; integration creation uses the same resolved scope for environment selection. Provider setup refreshes workspace metadata before resolving its scope or opening OAuth, and the OAuth completion continuation preserves the initiating scope for follow-up requests.This PR is stacked on parent PR #15805 and its
factory/rev-2383-environmentsbranch.Origin: https://warpdev.slack.com/archives/C0BREN45G2D/p1788501775785069
Linked Issue
REV-2383
Testing
./script/formatcargo clippy -p warp_cli -p warp_server_client -p warp --tests -- -D warningscargo nextest run -p warp_cli -p warp_server_client -p warp -E '<8 focused scope tests>'— 8 passed, covering CLI parsing, provider metadata service-boundary sequencing, completed OAuth team/teamless continuation, and public GraphQL header transportCARGO_TARGET_DIR=/tmp/warp-target ./script/presubmit— formatting, inline Rust test module validation, all Clippy configurations, clang-format, factory-file validation, and WGSL formatting passed. Full-workspace nextest completed with 11,713 passed and 38 sandbox-dependent remote/GUI failures outside the changed paths, primarily unavailable gcloud IAP credentials and workload-token runtime integration.Agent Mode