[AIGTWY-4759] Get the managed integration lanes green and add coverage - #699
Open
david-siqi-liu wants to merge 1 commit into
Open
david-siqi-liu wants to merge 1 commit into
david-siqi-liu wants to merge 1 commit into
Conversation
david-siqi-liu
force-pushed
the
david/aigtwy-4759-managed-diagnostics
branch
from
September 17, 2026 00:11
c24cf0d to
86622f6
Compare
david-siqi-liu
marked this pull request as ready for review
September 17, 2026 00:11
david-siqi-liu
requested review from
AarushiShah-db,
lilly-luo and
rohita5l
as code owners
September 17, 2026 00:11
david-siqi-liu
force-pushed
the
david/aigtwy-4759-managed-diagnostics
branch
2 times, most recently
from
September 17, 2026 01:14
c6c82ba to
fbc97d8
Compare
david-siqi-liu
force-pushed
the
david/aigtwy-4759-managed-diagnostics
branch
from
September 17, 2026 01:27
fbc97d8 to
3c4cab0
Compare
david-siqi-liu
force-pushed
the
david/aigtwy-4759-managed-diagnostics
branch
from
September 17, 2026 01:43
3c4cab0 to
e642107
Compare
The managed lanes 403'd because the managed workspace IP-blocked GitHub runners; that is fixed config-side (the E2E_ADMIN_* secrets repointed to runner-reachable ca-central plus a published CodingAgentConfig). This makes the lanes work and widens their coverage: - Install both agent CLIs in each managed lane, since a managed config enables both agents and `ug configure` applies it to every enabled agent (each lane previously installed only its own agent and failed configuring the other). - Add a managed idempotency CUJ: two `ug configure` runs apply the admin config to both enabled agents identically, which also guards the all-enabled-agents apply. Deterministic config-file assertions, no extra TUI. - Keep the lanes non-blocking until this path is proven stable on ca-central. Co-authored-by: Isaac <no-reply@databricks.com>
david-siqi-liu
force-pushed
the
david/aigtwy-4759-managed-diagnostics
branch
from
September 17, 2026 01:51
e642107 to
bd11153
Compare
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.
Why
The managed lanes were 403'ing because the managed workspace IP-blocked GitHub runners. That is fixed config-side: the
E2E_ADMIN_*secrets now point at runner-reachable ca-central, which publishes a matching CodingAgentConfig. This PR makes the lanes actually work and adds coverage.What
ug configureapplies it to every enabled agent, so a lane that installed only its own agent failed configuring the other (the Claude lane could not build the Codex catalog; the Codex lane hitFileNotFoundErrorforclaude).ug configureruns apply the admin config to both enabled agents identically, which also guards the all-enabled-agents apply. Deterministic config-file assertions, no extra TUI.continue-on-error) until this path is proven stable on ca-central; flipping to blocking and addingmanagedto the required gate is a follow-up.This pull request and its description were written by Isaac.