Conversation
hsadoyan
requested a deployment
to
integration
September 3, 2026 23:13 — with 
GitHub Actions
Waiting
GitHub Actions
Waiting
|
|
hsadoyan
force-pushed
the
harry/namespace-move-to-project
branch
from
September 4, 2026 21:41
cadf249 to
2b2fb21
Compare
hsadoyan
marked this pull request as ready for review
September 4, 2026 21:42
shakeelrao
previously approved these changes
Sep 16, 2026
hsadoyan
requested a deployment
to
integration
September 17, 2026 17:11 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
hsadoyan
force-pushed
the
harry/namespace-move-to-project
branch
from
September 17, 2026 17:35
08bd267 to
9eb2e3f
Compare
hsadoyan
added this pull request to stack #115
September 17, 2026 17:35
hsadoyan
requested a deployment
to
integration
September 17, 2026 17:35 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
hsadoyan
requested a deployment
to
integration
September 17, 2026 17:35 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
jeri-temporal
force-pushed
the
harry/namespace-move-to-project
branch
from
September 17, 2026 18:46
9eb2e3f to
56ae3b6
Compare
hsadoyan
force-pushed
the
harry/namespace-move-to-project
branch
from
September 17, 2026 23:31
56ae3b6 to
6e82634
Compare
Picks up MoveNamespaceToProject, published in cloud-api v0.22.0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Moves a namespace to a different project without recreating it, so running workers keep the namespace they are polling. Connectivity rules are project-scoped and must be chosen in the same call as the project. The selection is three-way and a repeated string flag cannot express all of it, so --no-connectivity-rules carries the explicit-none case: named ids attach those rules, --no-connectivity-rules asks for none, and omitting both asserts the namespace has no rules to carry over, which the server rejects when it does. The resource version is read from the namespace unless given, matching the other namespace commands. The expected source project is always explicit, since inferring it from the same read would defeat the concurrency check it exists to perform. Async surfacing goes through a new Poller.HandleOperation. The existing handlers each translate one rejection into an "already in the desired state" message, and the server treats a completed move as a success rather than rejecting it, so none of those translations apply. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
AsyncOperationHandler in the same package tree already declares a HandleOperation, so the generic name collided across the two async conventions and read like a shared helper the sibling handlers delegate to. The new name states what actually distinguishes it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
hsadoyan
force-pushed
the
harry/namespace-move-to-project
branch
from
September 17, 2026 23:32
6e82634 to
f686952
Compare
jeri-temporal
approved these changes
Sep 17, 2026
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
4 participants
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.
Moves a namespace to a different project without recreating it, so running workers keep the namespace they are polling.
The rule selection is three-way and a repeated string flag cannot express all of it, so
--no-connectivity-rulescarries the explicit-none case: named ids attach those rules,--no-connectivity-rulesasks for none, and omitting both asserts the namespace has no rules to carry over — which the server rejects when it does.The resource version is read from the namespace unless given. The source project is always explicit; inferring it from the same read would defeat the concurrency check it exists to perform. There is no
--idempotentflag — the server returns success for a completed move rather than the rejection that flag translates.Takes cloud-sdk v0.19.0, which carries the RPC published in cloud-api v0.22.0.
🤖 Generated with Claude Code