Cardano-config revamped with newer cardano-node options - #2080
Closed
jasagredo wants to merge 8 commits into
Closed
Conversation
jasagredo
force-pushed
the
js/cardano-config-revamped
branch
from
June 18, 2026 17:16
ae823a0 to
1ad4575
Compare
Introduce a new standalone cardano-config library that provides a single entry point for parsing the cardano-node configuration (CLI options and JSON/YAML files). Wire it into the cabal project and the cabal-gild CI script.
Add the configuration defaulting helper (Basics) and the types shared between the CLI arguments and the configuration files, such as NodeDatabasePaths (Common).
Add the optparse-applicative parser for the cardano-node command-line options (CliArgs), covering storage, credentials, host, tracing and shutdown options.
Add the FromJSON parsers for each configuration component: Storage (LedgerDB backend selection and snapshot policy), Consensus (Praos/Genesis mode), Protocol (per-era genesis files and hashes), Network, Mempool and Testing.
Add the top-level configuration file parser, which supports splitting the configuration across per-component sub-files and a ConfigurationVersion field (File), and resolveConfiguration, which combines the CLI arguments and the parsed files into a final NodeConfiguration.
Add example configurations, including a full single-file config and an example of splitting the configuration across per-component files.
jasagredo
force-pushed
the
js/cardano-config-revamped
branch
from
June 18, 2026 18:03
1ad4575 to
5c11514
Compare
Adopt the predictable-snapshots LedgerDB model from the upcoming node (f-f/prepare-11.1, predictable-snapshots): the LedgerDB Snapshots key is either a named policy (e.g. "Mithril") or an explicit options object (SnapshotInterval, SlotOffset, RateLimit, MinDelay, MaxDelay, NumOfDiskSnapshots), replacing the flat snapshot fields. The example configs are updated to match. The parsers remain hand-written FromJSON, for consumers who want the plain-JSON configuration without autodocodec.
Closed
Parse the LedgerDB @LSMExportPath@ key alongside @LSMDatabasePath@: an optional directory into which the LSM-tree backend exports snapshots as it takes them. Like the database path, it is only meaningful for the V2LSM backend, so it is carried as a second field of the V2LSM selector.
Contributor
Author
|
Superseded by IntersectMBO/cardano-base#671 |
github-project-automation
Bot
moved this from 🏗 In progress
to ✅ Done
in Consensus Team Backlog
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Includes changes from IntersectMBO/cardano-node#6604 and IntersectMBO/cardano-node#6526. Deprecated aliases are deleted.