Problem
Trusted Server runtime config loading currently has app-config defaults hardcoded in core. It does not derive the default config store id/key from the [stores.config] declaration in edgezero.toml.
This caused the runtime to look for app_config even when the manifest declares:
[stores.config]
ids = ["trusted_server_config"]
default = "trusted_server_config"
A temporary hotfix changed the hardcoded defaults to trusted_server_config, but that is not the right long-term behavior.
Desired behavior
- Runtime app-config loading should honor the manifest-defined default config id from
edgezero.toml.
ts config push/diff and runtime loading should agree on the same logical config id and blob key semantics.
- Avoid duplicated constants that can drift from the manifest.
Relevant files
edgezero.toml
crates/trusted-server-core/src/settings_data.rs
crates/trusted-server-core/src/config_payload.rs
crates/trusted-server-cli/src/run.rs
Notes
PR #864 is only a quick deploy unblocker and should be replaced with a proper manifest-driven fix.
Problem
Trusted Server runtime config loading currently has app-config defaults hardcoded in core. It does not derive the default config store id/key from the
[stores.config]declaration inedgezero.toml.This caused the runtime to look for
app_configeven when the manifest declares:A temporary hotfix changed the hardcoded defaults to
trusted_server_config, but that is not the right long-term behavior.Desired behavior
edgezero.toml.ts config push/diffand runtime loading should agree on the same logical config id and blob key semantics.Relevant files
edgezero.tomlcrates/trusted-server-core/src/settings_data.rscrates/trusted-server-core/src/config_payload.rscrates/trusted-server-cli/src/run.rsNotes
PR #864 is only a quick deploy unblocker and should be replaced with a proper manifest-driven fix.