Remove distinct in-memory config type #7566
Draft
+65
−68
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.
StartupConfigwas a near-identical copy ofCCHostConfigthat existed as a holdover from SGX/ringbuffer days. It added complexity by requiring conversion between types and duplicated field definitions. This consolidates them by makingStartupConfigan alias forCCFConfig.Changes
StartupConfigfields intoCCFConfig: Runtime fields (startup_host_time,node_data,service_data,sealed_ledger_secret_location) and nested types (Start,Join,Recover) now live directly inCCFConfigusing StartupConfig = CCFConfig;CCFConfigdirectlysnapshot_tx_interval: Was duplicate ofsnapshots.tx_countBefore/After
Files
include/ccf/node/startup_config.h- Consolidated typessrc/common/configuration.h- Updated JSON serializationsrc/host/run.cpp- Updated function signaturessrc/enclave/*.{h,cpp},src/node/*.h- UseCCFConfigOriginal prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.