CC-8364 Support Durable Object container settings and exports - #15597
Open
skepticfx wants to merge 1 commit into
Open
CC-8364 Support Durable Object container settings and exports#15597skepticfx wants to merge 1 commit into
skepticfx wants to merge 1 commit into
Conversation
🦋 Changeset detectedLatest commit: dc4afa8 The changes in this PR will be included in the next version bump. This PR includes changesets to release 10 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
workers-devprod
requested review from
a team and
dario-piotrowicz
and removed request for
a team
September 10, 2026 16:45
Contributor
|
Codeowners approval required for this PR:
Show detailed file reviewers
|
@cloudflare/autoconfig
@cloudflare/build-output-utils
@cloudflare/codemods
@cloudflare/config
@cloudflare/containers-shared
create-cloudflare
@cloudflare/deploy-helpers
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-functions
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-plugin
@cloudflare/workers-auth
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
Contributor
|
LGTM |
skepticfx
force-pushed
the
nafeez/CC-8364-do-application-configuration-wrangler
branch
from
September 11, 2026 04:40
5269712 to
b96799e
Compare
dario-piotrowicz
removed their request for review
September 11, 2026 09:59
skepticfx
force-pushed
the
nafeez/CC-8364-do-application-configuration-wrangler
branch
from
September 11, 2026 16:46
b96799e to
2098bc7
Compare
Resolve name-only Durable Object-managed Containers through declarative exports for validation, image preparation, version metadata, and application reconciliation. Apply explicit application-wide flags and log settings on deploy using POST for missing applications and PATCH for existing ones. Preserve omitted settings, existing settings during version commands, and rollout-none behavior. Cover name-only exports with settings across application creation, updates, uploads, and version deployment.
skepticfx
force-pushed
the
nafeez/CC-8364-do-application-configuration-wrangler
branch
from
September 11, 2026 17:42
2098bc7 to
dc4afa8
Compare
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| ): Promise<void> { | ||
| let existing: DurableObjectApplicationState; | ||
| try { | ||
| existing = await ApplicationsService.getApplication(namespaceId); |
Contributor
There was a problem hiding this comment.
🔴 Existing applications look missing
On redeploy, applyApplication queries the application endpoint with a namespace ID. Application stores its ID and namespace separately, so Wrangler retries creation and fails on the duplicate.
Learn more
The application API addresses GET /applications/{application_id} by application ID. A Durable Object-backed application stores that ID separately from durable_objects.namespace_id in Application. The code only has a namespace ID here, so a previously created application is not reliably addressable through this endpoint. A 404 then enters the create path, where the namespace already owns an application and the deployment fails instead of updating or preserving settings.
Example: Namespace ns-123 owns application app-456. A second deploy requests /applications/ns-123, receives 404, and POSTs another application for ns-123; the API rejects it as already attached.
Recommended fix: Resolve the application by its Durable Object namespace before calling getApplication or modifyApplication. Use an SDK endpoint that filters by namespace if available, or list applications and match durable_objects.namespace_id, then retain the returned application.id for PATCH. Preserve the existing identity checks against the matched application.
Was this helpful? React with 👍 or 👎 to provide feedback.
This was referenced Sep 14, 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
2 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.
Fixes #CC-8364
Resolve name-only Durable Object-managed Containers through declarative exports for validation, image preparation, version metadata, and application reconciliation.
Apply explicit application-wide flags and log settings on deploy using POST for missing applications and PATCH for existing ones. Preserve omitted settings, existing settings during version commands, and rollout-none behavior.
Cover name-only exports with settings across application creation, updates, uploads, and version deployment.