Skip to content

Add native AWS store providers - #414

Open
ChristianPavilonis wants to merge 22 commits into
issue-397-diagnostics-proxy-trust-specfrom
issue-410-native-store-providers
Open

ChristianPavilonis wants to merge 22 commits into
issue-397-diagnostics-proxy-trust-specfrom
issue-410-native-store-providers

Conversation

@ChristianPavilonis

@ChristianPavilonis ChristianPavilonis commented Oct 8, 2026 •

Copy link
Copy Markdown
Collaborator

Current review readiness

Ready for review. Required current-head CI passed at c66f93f118141a2ed7469a8ab96b12902f3854e6: test run 42924131967.

Minimal fixes originate in #414 and are merged upward:

  • Typed SDK connector timeouts map to Deadline; non-timeouts remain Unavailable. The previously failing hosted timeout test and all 78 provider cases now pass without assertion, retry or duration changes.
  • Fresh consumers use the existing locked SDK cohort: optional native aws-types =1.6.0 and aws-smithy-runtime-api =1.19.0. This prevents the schema mismatch and preserves the explicit older behavior version instead of switching retry policy or suppressing deprecations. A fresh consumer passes with compiler and Clippy warnings denied throughout.
  • The constructor-boundary test attempts the full upload while independently reading and requiring a complete, finite expected response. The existing startup-readiness poll treats a connection reset as not yet HTTP-ready within its unchanged deadline; success still requires a complete HTTP200 and the original payload checks. Production transport and limits are unchanged.

Local final-top Axum checks pass 488 unit, 28 contract, six AWS startup, four celld startup and 36 hosting cases. Final-top workspace strict Clippy and formatting pass. The prior stable checkpoint passed all six mandatory commands; unchanged inputs retain their receipts, while fresh current-head CI checks the combined state. The current ready state supersedes historical draft-only prerequisites below; unexecuted deployment acceptance is not claimed complete. An additional Fastly WASM runtime job was still running at transition and is not counted as passed. No TS work or deployment qualification is a review prerequisite. Integration #462 remains draft; reviewers aram356, prk-Jr and dhruv8sh remain requested. Stack465 and PR bases are unchanged; #453 is excluded.

Current review-stack checkpoint

Publication head: c66f93f118141a2ed7469a8ab96b12902f3854e6. This cleanup preserves the existing feature unit and PR identity. The additional change is the completed generated-native build correction: image-only code now follows the scaffold's existing Fastly-example selection, with no request-policy change. Its focused generator/native proof is retained; fresh per-branch hosted checks are not assumed green.

Review order: #275 → #406 → #407 → #409 → #414 → #422 → #439 → #454. Draft integration checkpoint: #462. New SDK/group/codec/phase development and unrelated TS work are not prerequisites or additions to this PR. Earlier notes below retain their original tested revisions and limits; they are not a whole-tree pass for this new head.

Earlier implementation and proof notes

RC refresh checkpoint, 2026-11-10

Current head: 48761e3e528eae0481e9f6e2eb30c0002f00d239.

Only the AWS provider delta is replayed onto the updated hosting/diagnostic stack. Duplicate historical foundation/hosting commits are omitted. Explicit production options and initializer startup have a TCP no-ambient-merge regression. Ordinary test PR coverage remains unfiltered; an old donor filter was removed again.

Feature proof passes 417 Axum unit, 5 AWS startup, 33 hosting, 74 AWS provider, 256 CLI unit and 15 Node runner cases, scoped strict Clippy and SDK-isolation checks. Parent namespace/CI composition reruns pass all 5 AWS startup, 33 hosting and 35 Node CI cases. All five tracked locked fetches pass.

Generated native consumer/DynamoDB and pinned disposable-service runtime proofs are still pending integration execution. Bounded retained SDK values are not an RSS cap; timeout cancellation does not prove blocking credential work stopped. AWS clients intentionally retain their normal credential chain, separate from explicit hosting-source selection. No cloud acceptance is claimed.

Draft pending fresh hosted checks and the combined RC audit. Two unchanged native default-parallel deadline misses remain recorded and unclassified; serial passes and untouched-foundation parallel passes do not clear them. No timing bound was relaxed. No deployment, main merge, security-alert dismissal or review-thread resolution occurred. Historical design/review context follows.


Summary

  • Select local, supplied or built-in native stores independently per logical ID, without changing portable store traits or requiring Send setup futures.
  • Add default-off AppConfig Agent and Secrets Manager immutable startup snapshots, plus independently selected live DynamoDB ordinary KV.
  • Preserve shared config/secret preparation quotas/deadlines and complete registries before the application initializer/listener. Wire generated features, SDK-free structural CLI validation and AWS-bound config-push refusal.

Design and boundaries

This adds native store providers, not a new HTTP runtime. edgezero-store-aws implements the existing core store traits and does not depend on Axum. Axum owns provider selection and startup composition; core owns portable handles, per-ID registries and typed configuration resolution.

The portable edgezero.toml declares logical store IDs and defaults. AWS resource references belong in a separate versioned native bindings document, selected through an absolute file path in EDGEZERO__STORE_BINDINGS_FILE or through explicit AxumRunOptions. Applications can also supply ready handles or non-Send deferred setup, without a plugin registry.

Each declared ID selects one supplied, explicitly bound or implicit local source. Supplied/file collisions and undeclared IDs are rejected. The runner validates all sources before opening runner-owned local stores or polling deferred setup. CONFIG_DIR/DATA_DIR are required only for remaining local bindings. An unavailable selected provider fails startup; it never falls back to local data.

Provider Store contract Runtime behavior
AppConfig Agent Whole-document ConfigStore reads Immutable startup snapshot; restart to adopt changes
Secrets Manager Whole-value SecretStore reads Immutable startup snapshot; restart to adopt changes
DynamoDB Ordinary KvStore operations Live storage with fresh per-operation budgets
flowchart TD
    Bindings[Bindings and supplied inputs] --> Validate[Validate sources and compiled providers]
    Validate --> Prepare[Assemble app and prepare stores in the native runtime]
    Prepare --> Registries[Complete per-ID registries]
    Registries --> Initialize[Run app-owned initializer when supplied]
    Initialize --> Serve[Bind listener and serve requests]
Loading

One shared AWS preparation session owns startup budgets, client reuse and snapshot deduplication. The initializer receives the same registries used by requests. The application chooses its required config keys, schemas, secret checks and retained startup state; the framework does not infer those requirements or promise an atomic revision across remote resources.

AWS features are default-off and native-only. Existing entrypoints retain their local defaults; newly generated entrypoints select strict startup only when the bindings-file locator is present. Trusted Server adoption is separate work, and this does not claim a source-compatible upgrade from older EdgeZero versions across the #275/#406 prerequisites.

Diagnostic limitation: EdgeZero-owned errors/debug output discard or redact provider details. AWS SDK/dependency DEBUG/TRACE is not suppressed and can expose resource names and credential-source metadata. DynamoDB model Debug can also expose item keys and values, including binary hex, without enabling sensitive-body logging. LOG_SENSITIVE_BODIES=true can expose further response details. Operators must review dependency logging filters. No scoped/global subscriber suppression or application-wide logging policy is installed.

Stack and scope

Existing draft stack member based on docs/outbound-http-spec / #275 at ea66eff045512cccc60646d6ec339e83ff44fed7, with the compatible #406 production lifecycle bridge. Neither prerequisite PR was rewritten or merged. The user approved adding DynamoDB on this same branch/PR and committing/pushing it after checks.

Real AWS/IAM/capacity/deployment/image acceptance remains explicitly excluded. No real AWS service calls, infrastructure changes, image pulls or deployments were performed. SDK fixtures use dummy credentials, isolated or bypassed profile discovery, and literal-loopback endpoints.

DynamoDB KV

  • Independent default-off dynamodb-kv provider / generated aws-dynamodb feature; existing aws-stores remains AppConfig Agent + Secrets Manager only.
  • Strict v1 [kv.<id>] binding with explicit region/table/physical namespace, no credential or endpoint fields. Normal operator-owned SDK credential/endpoint policy remains supported.
  • Operator-owned ACTIVE, single-region, unindexed String pk/sk table; bounded DescribeTable preflight, exact table-name/schema checking, no provisioning or local fallback. All-remote KV needs no DATA_DIR.
  • Exact UTF-8 keys and arbitrary/empty binary values; 384 KiB payload cap. Millisecond logical expiry plus rounded-up service TTL; ordinary Put clears expiry and expired reads never delete renewed rows.
  • Strong Get/ascending base-table Query, one Query per page, scoped/versioned bounded cursors. Short/empty pages with continuation are valid. No CAS, atomic read-modify-write, snapshot pages or distributed identity-graph guarantee.
  • Fresh bounded runtime deadlines; one SDK attempt, no retry loop. Put/Delete can commit before returning an error. DescribeTable does not certify deployed IAM/write permissions/capacity.

DynamoDB is live storage, not a retained startup snapshot. The existing default 8 MiB retained-payload cap is per shared config/secret preparation session, not process/RSS or live database contents. Config/secrets still adopt remote changes only on restart; no live config/secret refresh or mutation is added.

Bindings validation remains structural-only / provider availability unknown. No offline Cargo resolver or guessed availability verdict is shipped. Custom shell actions remain untouched.

Verification

Original snapshot phase: all 24 post-rebase gates passed at its recorded source checkpoint; historical evidence remains in the original spec/plan and /tmp/native-store-integration/final-checks/. This does not claim those old results prove the later DynamoDB edits.

DynamoDB extension: 20 code gates plus docs lint/full-format/build passed, against an archived exact staged source tree independent of eight pre-existing dirty files. SHA-256 input manifests matched; later publication-record edits are Markdown-only.

  • Workspace default tests: 1,999 passed, 0 failed, 16 ignored; required native/provider feature scopes and generated consumers executed separately, not a claim that every unrelated ignored test ran.
  • Provider library: DynamoDB 44, Agent 26, Secrets 26, combined 74.
  • Native DynamoDB-only library 229; all-feature native test/doc suites 302.
  • Actual CLI-generated DynamoDB consumer: default-off refusal before SDK I/O, enabled put/get/list/TTL-write/read, retained data after restart, and delete.
  • Existing actual CLI-generated AppConfig/Secrets consumer rerun successfully.
  • Strict workspace all-target/all-feature Clippy; isolated provider scopes; native default Clippy; strict provider/native rustdoc; fmt.
  • SDK isolation, unchanged aws-stores membership, Cloudflare/Fastly/Spin WASM checks.
  • Actual SDK wire/shared KV contracts, Unicode NFC/NFD, binary/empty/size/key boundaries, millisecond expiry/renewal/reset, malformed expiry, short/empty continuation pages, cursor/table scope, closed denial/missing/stall errors.
  • Ambiguous Put/Delete fixtures apply the mutation before a scripted 500, then verify Unavailable, one attempt and the retained/removed row. SDK model Debug disclosure is directly asserted.
  • Mixed DynamoDB/local/ready/non-Send deferred source validation without polling/opening another local store; existing generic native staging atomicity/drop tests preserved.
  • Separate end-to-end generated edgezero serve invocation; shared argument/action selection has unit/source proof, generated build and startup are executed.
  • Real AWS acceptance, intentionally excluded; fixtures do not establish deployed IAM/capacity or the service's 1 MiB evaluation boundary.

An inherited Secrets timeout test transiently returned Unavailable instead of Deadline under the combined parallel run. It passed alone, then all 74 provider tests passed serially. The initial failure log is retained; no production/unrelated test was changed to hide it.

Commands/fingerprints: /tmp/dynamodb-baseline/final-checks.sh, /tmp/dynamodb-baseline/final/, snapshot-{before,after}.sha256; checked source tree 2fa76fb26377cf41203c255f924d988d6b657002. Final read-only provider review found no confirmed defects and is separate from executed checks.

Closes

Closes #410

Checklist

  • Portable store traits and handles unchanged; native AWS dependencies feature/target gated
  • Per-ID KV/config/secret registries; non-Send setup preserved
  • Source-free owned errors, no subscriber suppression
  • Deterministic actual-SDK loopback proof; no real credentials committed
  • Unrelated baseline hunks in eight modified files preserved and excluded from the DynamoDB commits

Fixture lifetime follow-up

Commit e9181716975c068cd6894e046eec1ee3e194ad69 keeps the loopback endpoint alive until its SDK child completes. A local reproduction of the hosted timeout failure identified a genuine ConnectionRefused after the one-response worker dropped its listener while the SDK still owned retries. The deterministic endpoint-lifetime regression fails before this fix. All 79 AWS tests, strict all-feature/all-target AWS Clippy, and 30 repetitions of the original timeout test pass afterward. This changes only the test fixture. Production timeout limits, retry policy and typed error classification are unchanged. Current-head hosted qualification is running; no release tag is claimed.

Owned follow-up review checkpoint

  • Branch advanced through an ordinary merge; every previous public head remains an ancestor.
  • Current head: 4adeb228ebcc0839f5306e16be6ea9b963e97f36. Source tree 224f1f81634a5871a05b569939b13a4f02606b0d is byte-identical to previous head 3733482f6bedcaecb162b1e927209f3800f8b388.
  • Related owned draft: #499. It is intentionally a placeholder until the author cleans feat: implement portable outbound HTTP and request lifecycle contracts #275 and the owned baseline/follow-up are reconciled.
  • Review base and ready/draft state are unchanged. The feature-only review diff is byte-identical to the pre-update diff.
  • Existing qualification remains tied to its recorded inputs. New hosted outcomes are reported separately; this history update does not qualify new source-version-bound binaries or move a release tag.

@ChristianPavilonis ChristianPavilonis self-assigned this Oct 8, 2026
@ChristianPavilonis ChristianPavilonis changed the title issue 410 native store providers Add per-ID native AWS store providers Oct 8, 2026
@ChristianPavilonis ChristianPavilonis changed the title Add per-ID native AWS store providers Add native AWS store providers Oct 14, 2026
@ChristianPavilonis
ChristianPavilonis marked this pull request as ready for review October 19, 2026 18:50
@ChristianPavilonis
ChristianPavilonis requested review from aram356 and prk-Jr and removed request for aram356 October 19, 2026 18:50
@ChristianPavilonis
ChristianPavilonis marked this pull request as draft October 19, 2026 19:10
@ChristianPavilonis
ChristianPavilonis removed this pull request from stack #430 October 22, 2026 15:23
@ChristianPavilonis
ChristianPavilonis changed the base branch from docs/outbound-http-spec to issue-397-diagnostics-proxy-trust-spec October 22, 2026 15:23
@ChristianPavilonis ChristianPavilonis added this to the 202611 milestone Oct 22, 2026
@ChristianPavilonis
ChristianPavilonis force-pushed the issue-410-native-store-providers branch from 5dc18fe to 63892b0 Compare November 10, 2026 19:54

@prk-Jr prk-Jr left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

PR Review

Summary

Reviewed at 3733482f. The commits since the previous changes-requested review (at c66f93f) only merge the stack and repair fixtures, so the blocking findings from that review still apply at this head. This pass adds one documentation blocker and several smaller items. Requesting changes because the earlier blockers are still open.

😃 Praise

  • Every level of the bindings TOML is deny_unknown_fields, including the internally tagged provider enums and the nested limit tables. The file-type check uses the opened handle, so there is no type race between checking and reading.
  • Every Axum feature combination compiles: none, cli, native-bindings, axum, each aws-* alone, and aws-stores. With no AWS feature, a bindings file fails closed with UnsupportedProvider before any local store opens.
  • The listener binds only after source validation, store preparation and the initializer complete.

Findings

Earlier blockers still open at 3733482f

  • 🔧 run_app still ignores EDGEZERO__STORE_BINDINGS_FILE. Only run_generated_app reads it (dev_server.rs:990 vs :1017). The demo and the axum.md entrypoint still call run_app.
  • 🔧 The AWS fixtures still fail on macOS. cargo test -p edgezero-store-aws --all-features --lib failed in three runs at this head (2, 3 and 1 of 79 failed) with read request headers: Os { code: 35, kind: WouldBlock }. Commit e9181716 keeps the listener alive longer but does not make accepted streams blocking.
  • 🔧 Unchanged at this head:
    • The UPDATING table status is still rejected (dynamodb_kv.rs:687).
    • SDK connectors still accumulate under tight limits (dynamodb_kv.rs:634).
    • The docs contradictions are still present.
    • CI still runs no axum lib tests with an aws-* feature.
    • The two open questions (local secret IDs sharing env variables, container pulls in the required CLI job) have no answer yet.

New, blocking

  • 🔧 The guide's config push command cannot reach the guard it describes (docs/guide/native-aws-stores.md:281, inline). This belongs with the existing docs blocker.

New, non-blocking

  • 🤔 Secret name length is validated on a trimmed value, but runtime uses the untrimmed one (native_bindings.rs:600, inline).
  • 🤔 The env-selected bindings file cannot use non-default trusted limits (run_options.rs:293, inline).
  • 🤔 A compiled-out AppConfig provider is reported as a missing token (run_options.rs:183, inline).
  • ⛏ Setting one timeout limit alone can be rejected because of another field's default (settings.rs:187, inline).
  • ⛏ The CLI reference does not list the new flags. docs/guide/cli-reference.md has no --adapter, --store-bindings, --target, --target-features, --target-all-features or --target-no-default-features for config validate, and no --store-bindings for config push. It also does not mention that --adapter axum on validate switches to bindings-only mode. This file is not in the diff, so the finding goes here.
  • ⛏ "Existing" wording in dynamodb-kv.md (docs/guide/dynamodb-kv.md:18, inline). This is a sibling of the earlier native-aws-stores.md wording comment.
  • 📝 Addition to the earlier read-cap comment (dynamodb_kv.rs:357). get_bytes checks max_value_bytes before the expiry filter (:354-367). A row that is over a lowered cap and has also expired therefore returns Unavailable instead of reading as absent, until the DynamoDB TTL sweep removes it. Capping reads at the fixed 393,216-byte maximum, as already suggested, fixes both cases.
  • 📝 The CodeQL clear-text logging alert on scripts/native_aws_test_admin.mjs looks like a false positive. The script only accepts a literal http://127.0.0.1:<port> endpoint with a dummy SigV4 header. The logged result holds hard-coded fixture values, and stdout is the IPC channel to the Rust test. Dismissing it as test fixture data seems reasonable.

CI Status

  • GitHub Actions at 3733482f: all checks pass.
  • Local, macOS, at 3733482f: edgezero-store-aws --all-features --lib fails intermittently, as described above.
  • cargo check across the Axum feature matrix: passes.
  • Axum lib native_/run_options tests with aws-stores,aws-dynamodb,test-utils: 70 passed.
  • CLI lib bindings/push tests: 10/10.
  • Node native_aws_* tests: 16/16.
  • Not run: the Docker emulator suite, the ignored generated-build proofs, and anything against real AWS.


## Push remains local

`edgezero config push --adapter axum` writes local config snapshot files. It does not publish

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

🔧 This command cannot reach the push guard described here

The bundled edgezero binary parses config push as ConfigCmd::Push(ConfigCmdStubArgs) (args.rs:100). That stub accepts any flags, --store-bindings included, and run_config_push always returns the "requires the typed downstream CLI" error (config.rs:314-322). cli-reference.md says the same.

Scenario: an operator copies edgezero config push --adapter axum --store-bindings /abs/bindings.toml. The command exits with the stub error. They never see the AWS-binding refusal, and nothing is written locally either.

Fix: use the typed CLI form here, as blob-app-config-migration.md does:

<your-app>-cli config push --adapter axum --store-bindings /absolute/path/bindings.toml

}
if kind == "secrets" && source != NativeBindingSource::Supplied {
let namespace = if source == NativeBindingSource::Local {
env.store_setting(kind, id, "name").map_or(id, str::trim)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

🤔 The length check measures a trimmed name, but runtime uses the untrimmed name

For local secret IDs this checks store_setting(...).map_or(id, str::trim) against MAX_NAME_LEN. The runtime store is built with options.env_config().store_name("secrets", id) (dev_server.rs:1467). EnvConfig::store_name (env_config.rs:170-174) filters out only blank and control values; it does not trim.

Scenario: EDGEZERO__STORES__SECRETS__SIGNING__NAME holds 512 bytes plus a trailing space. Startup accepts it and reports Ready. Then every SecretHandle::get_bytes call fails validate_name with 513 bytes. The fail-fast this check exists for (secret_namespace_limits_are_checked_before_preparation) becomes a failure on every request.

Fix: measure what runtime uses, env.store_name(kind, id).len(), or trim in both places.

}
}
}
if let Some(path) = options.env.get(&["store_bindings_file"]).map(str::to_owned) {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

🤔 With an env-selected bindings file, the trusted file limits cannot be changed

from_vars selects the bindings file as soon as the locator is present, using the default NativeBindingsLimits (256 KiB, 128 IDs). Any later with_native_bindings_limits call is rejected with "limits must precede selection" (:470-487). The NativeBindingsLimits doc presents these as host-controlled trusted bounds. On the env-located path, which from_env, run_production_app and run_generated_app all use, the host has no way to set them. A larger deployment has to drop from_env and rebuild every hosting setting by hand.

Fix: record the locator in from_vars and read the file lazily, either at plan validation or the first bindings() call. Alternatively, add a from_env_with_limits(limits) constructor.

}
let mut options = Self::from_vars(pairs)?;
options.non_unicode_overrides = non_unicode;
// Only this env-loading boundary may resolve named token variables.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

🤔 A compiled-out AppConfig provider is reported as a missing token

capture_agent_tokens runs on the env-loading path whatever features are compiled. Suppose a binary built without aws-appconfig-agent loads a bindings file with [config.x] provider = "aws-appconfig-agent" and access_token_env = "T", and T is unset. Startup fails with the Agent-token-absent error before the capability check (native_stores.rs:258-271) can report "provider not compiled". That sends the operator after a token, when the actual fix is a Cargo feature.

Fix: skip token capture when !cfg!(feature = "aws-appconfig-agent"), or run the provider-capability check before capturing tokens.

if self.max_value_bytes == 0
|| self.max_value_bytes > 393_216
|| self.connect_timeout_ms == 0
|| self.connect_timeout_ms > self.attempt_timeout_ms

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

⛏ Setting one limit alone can fail because of another field's default

Unset fields are filled in by #[serde(default)], then connect <= attempt <= operation is enforced. Setting only operation_timeout_ms = 1500 keeps the default attempt_timeout_ms = 2000, so validation returns InvalidLimits without naming any field. AwsPreparationLimits::validate has the same behaviour (:475-477).

Fix: document the ordering rule next to the limits, or clamp unset attempt and connect defaults to the configured operation timeout.

Comment thread docs/guide/dynamodb-kv.md
features = ["aws-dynamodb"]
```

`aws-stores` retains its existing AppConfig Agent and Secrets Manager membership.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

⛏ "aws-stores retains its existing AppConfig Agent and Secrets Manager membership". aws-stores is introduced in this PR, so it has no earlier membership for readers to rely on. This is a sibling of the wording comment on native-aws-stores.md. Suggest: "aws-stores enables AppConfig Agent and Secrets Manager only."

@aram356

aram356 commented Nov 13, 2026

Copy link
Copy Markdown
Collaborator

CREATOR: From the server-side identity plan (IABTechLab/trusted-server#1559, c7dc9de77): Drop those two commits once they move down.

Part of #488

aram356 added a commit that referenced this pull request Nov 14, 2026
Brings #275 at e9ffaa8 and the refreshed heads of #499, #460, #406,
#407, #409, #414, #422 and #439. Each PR merged the one below it, so
this merge has no conflicts.

Two edits fit #469 to #275, as #469's open review asks:

- #469's ingress JA4 test calls into_core_request with one argument.
  #275 now passes the Axum outbound executor through that function, so
  the test gets an executor handle the way the other ingress tests do.
- The Axum guide names EdgeZeroAxumService, which #275 removes and
  check_outbound_legacy_api.sh rejects. The guide now names only
  AxumDevServer::with_trusted_ja4_header.
aram356 added a commit that referenced this pull request Nov 16, 2026
Brings #275 at b65e714 and the refreshed heads of #499, #460, #406,
#407, #409, #414, #422 and #439. Each PR merged the one below it, so
this merge has no conflicts. #409 resolved the one conflict on the way
up, in edgezero-core's app.rs imports, by keeping both.
aram356 added a commit that referenced this pull request Nov 17, 2026
Brings #275 at ea2549f and the refreshed heads of #499, #460, #406,
#407, #409, #414, #422 and #439, including #422's stock-celld store
service and its merge into #439. Each PR merged the one below it, with
no conflicts on the way up, so this merge has no conflicts.

This branch has not been deployed

No deployments
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.

Add native AWS configuration, secret, and ordinary KV store providers

5 participants