BugShippedExtensionsPublic

#3909 kubernetes: externalsecret and normalizeMeta follow-ups from #3907

Opened by stack72 · 10/25/2026· Shipped 10/25/2026

Follow-ups from the verification reviews of swamp-club #3907 (externalsecret model and the last-applied-configuration fix). None blocked the gate.

Misleading error on v1beta1-only installs. With no apiVersion pinned, externalsecret get or forceSync on a missing object retries v1beta1 and rethrows the v1 error. On an older ESO that serves only v1beta1, that v1 error is the generic "the server could not find the requested resource", which reads like "CRD not installed". The real API server's 404 for a missing object carries details.name, so prefer the 404 whose Status names the object (externalsecret.ts, withVersion).
Namespace collision in stored records. externalsecret writes instances by object name only, so same-named ExternalSecrets in different namespaces overwrite each other's record. Every other kubernetes model does the same; fix once for the extension if it is fixed at all.
Extra round trip. A missing object costs a v1 and a v1beta1 request when no version is pinned. A one-time discovery call on /apis/external-secrets.io, or caching the served version per client, would remove it.
Repeated force-sync value. forceSync uses new Date().toISOString(); two calls in the same millisecond (parallel workflow steps) send the same value and the second is a no-op. Append a random suffix if this matters.
Other spec-copying annotations. normalizeMeta now drops kubectl.kubernetes.io/last-applied-configuration, which carried plaintext Secret values into secretMeta. Other tools copy specs into annotations too (Helm, Argo CD tracking); decide whether to filter those for the secret model.
Test fake comment. fake_api_server.ts answers 415 to any PATCH that is not merge patch. Add a comment that a model using strategic-merge or JSON Patch needs the fake extended first.

10/25/2026, 12:57:48 PM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack7210/25/2026, 12:13:51 PM

system commented 10/25/2026, 11:55:19 AM

Classified automatically when this issue was filed.

Type: Bug
Source: Extensions

If you feel this classification is incorrect, add a ripple to tell us so.

Move the Zod argument-field extractor into @swamp-club/extension-scoring so the CLI and registry read schemas alike

Docs: extension quality scores with the registry formula and reports grade (swamp-club#3845)

serve: dispatch to an idle worker waits for its worker_busy write on the shared gateway transition tail

serve: worker enrollment resolves and creates the worker definition inside the serialized gateway transition tail

Datastore rework Phase 5 (team mode) 2/3: the CLI's serve upstream — with serverAddress, a v3 checkout commits, reads chunks and catches up through serve's datastore API, with no storage credentials

Extension dependencies: the shared import scan reads Babel syntax, not tokens (follow-up to #3969)

Rescore every extension's current version under rubric v5

Extension scoring queue: two replicas can claim the same pending event

Scheduled flaky-test detection is failing

Manual: the supported extension dependency categories, the canonical form and the lock rule, rewritten once against the final design

Registry audits v2 extension archives as written, and a range costs the loose point only without a valid lock

Extension consumers keep the publisher's bundle: pull, update and auto-resolve stop rebuilding (direction A for #3634)

Extension push: inputs that open up (workspace root lock, ancestor config refused by name, JSR dist-tags) and the skill docs rewritten once

Extension push ships the canonical form: every npm:/jsr: import pinned exact, and a v2 dependency-audit.json

stagecraft studio ticket columns: round-5 review lows from #3828 (source watch cost, relationText lookup, cross-instance claim)

A long-lived serve client for extensions, and a stable rate_limited error code

swamp serve on a v3 datastore never settles a workflow run left running by a stopped instance: boot reaper skips it as belonging to a remote instance

swamp serve on a v3 datastore: a run interrupted at a clean shutdown is never committed when the bucket is slow, and stays running for every other checkout

Support creating 1Password vaults for new clients

Filesystem datastore: an unclean shutdown leaves zero-byte data versions as the latest version, and `doctor datastores --repair` does not detect them

datastore_v3_replica_verify_test stall case flakes under the full integration run: restore.pid is read before the stub writes it

Generated state schemas require every child of nested objects, so normal resources warn on create/get

Add LinkedIn as a login provider

Showcase reward backfill can double-pay 5,000,000 points when replicas start together

Showcase editor: caption counter is not announced to screen readers

Profile showcase read: approved list sorts on review.reviewedAt in memory

Showcase countByStatus: $match live statuses before the $group

Showcase admin queues: index-serve the updatedAt sort on approved/rejected

Annotate and retain past workflow runs and data after the fact

Docs: --trusted-hosts accepts host:port for public addresses on non-default ports

A workflow step's method output is invisible to `data query` and `data list`, and the method summary's retrieval command returns an older run's data

Skill propulsion rule is silent when no transition is satisfied because stage work is outstanding

package.json mode: no loose-specifier warning for a range push ships as the exact installed version

extension fmt (and any command) creates or rewrites deno.lock when the extension lives in the repo's loaded extensions/ dir

serve shutdown does not wait for worker status writes, and its listener accepts workers after the gateway is disposed

stagecraft: rename work mode `method` to `behavior`, matching swamp's rename of models to behaviors

auth token create --json fields key and signinToken are undocumented; no token-mode service setup page

trigger.schedule is evaluated in the serve host's local time zone, with no zone field and no doc saying so

workflow validate/run say "Workflow not found" for a file that doctor workflows explains is misnamed

telemetry stats says "No telemetry data found" right after successful sends; say the spool is empty because it flushed

Docs: publish typed-secrets Phase 4.6 expression and delivery semantics

Extension registry page: a supported way to include media (images) in the README

CEL: data.latest(...).version is a double, but data.version() only accepts int, so "version - 1" fails at run time

workflow resume --run refuses workflows with the same step name in two jobs, though validate and run accept them

Update public OpenTelemetry manual for remote waterfalls and execution metrics (#3786)

Server-driven warning and info messages to CLI users, targeted by swamp version (exploration)

Serve: delegate namespace-scoped extension pulls and reload without granting administrator access

workflow cancel --server ignores --ca-cert and SWAMP_CA_CERT

Preserve active worker execution across serve restarts and upgrades; reconnect and reattach dispatches

v3: chunk durability barrier costs a full drive-cache flush per command on macOS; use an ordering barrier

vary/forEach object values with no key/name/id produce data names Windows refuses

issue-lifecycle start drops issue comments: context.comments is always empty

swamp core: a non-string sensitive value reads back as a JSON string

Generated vault keys carry raw data-name and vary characters that strict vault providers reject

bundleExtension 'bundles on different caches do not wait for each other' test fails under CPU load

Relationships

#3909 kubernetes: externalsecret and normalizeMeta follow-ups from #3907

Shipped