Skip to content

feat: Update Regional Access Boundary#12867

Open
vverman wants to merge 1 commit intogoogleapis:regional-access-boundariesfrom
vverman:rab-clean
Open

feat: Update Regional Access Boundary#12867
vverman wants to merge 1 commit intogoogleapis:regional-access-boundariesfrom
vverman:rab-clean

Conversation

@vverman
Copy link
Copy Markdown
Contributor

@vverman vverman commented Apr 20, 2026

  1. The RAB refresh uses a direct executor with a fixed thread pool as opposed to instantiating a new thread each time.

  2. The RAB env gate -> GOOGLE_AUTH_TRUST_BOUNDARY_ENABLE_EXPERIMENT has been removed. This means RAB refresh triggers by default.

  3. Added other fixes/suggestions made in the previous Java PR.

@vverman vverman requested review from a team as code owners April 20, 2026 22:06
@vverman vverman requested review from lqiu96 and nbayati April 20, 2026 22:08
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request refactors the RegionalAccessBoundary and RegionalAccessBoundaryManager classes to improve resource management and testability. Key changes include replacing environment-variable-based feature toggling with a ThreadLocal mechanism for tests, migrating from manual thread creation to a bounded ExecutorService for asynchronous refresh tasks to prevent resource exhaustion, and ensuring HTTP responses are properly disconnected in a finally block. Additionally, the test suite has been migrated to JUnit 5, and several tests were cleaned up by removing deprecated environment provider mocks. I have no feedback to provide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant