Skip to content

Add native celld configuration and KV store providers #437

Description

@ChristianPavilonis

Description

PR #422 adds native celld configuration snapshots and live ordinary KV through the embedded scoped API, on #414 native-provider infrastructure. It stays open for stack integration, service artifact availability and acceptance. This is celld store delivery, separate from the still-open runtime requirement #421 and its closed, unmerged previous PR #420.

Steps to reproduce

Select config and KV independently per logical ID on a generated native application. Test default-off refusal, mixed AWS/celld/local bindings, preparation budgets, redacted failures and startup ordering. Reproduce opt-in scoped-service acceptance against an identified reviewed artifact.

Expected behavior

Explicit default-off provider selection produces immutable config snapshots and live KV without changing portable traits or HTTP runtime ownership, with separate AWS/celld credentials and bounded work.

Impact

Local fixtures do not establish the availability/behavior of the companion service artifact or certify fleet forwarding, reload/failover, replication, production isolation or sustained stress.

Proposed fix

Review/integrate #422 after accepted prerequisites, retain per-ID bindings/feature isolation/generated consumers and document exact service/API dependency and acceptance limits. No celld Worker adapter, identity lifecycle Add/CAS, config hot reload or deployment/fleet certification is included.

Done when

  • Review and merge Add native celld config and KV store providers #422 after integrating its prerequisite stack.
  • Pass relevant provider, native startup, feature-isolation and generated-consumer checks against the revision being merged.
  • Resolve or explicitly retain the documented dependency on the companion celld scoped API, with reproducible service acceptance and an available reviewed artifact.
  • Preserve the PR's documented proof limits. Fleet forwarding, reload/failover, production isolation, replication/storage acceptance and sustained stress are not certified by local tests.

Detailed verification and remaining draft gates are recorded in #422. Related native-provider work is tracked in #410; portable store traits and HTTP runtime ownership remain unchanged.

Related

Metadata

Metadata

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions