Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mx 14997 overwrite config structs #5851

Merged
merged 9 commits into from
Feb 1, 2024
Prev Previous commit
Next Next commit
more examples in prefs toml
  • Loading branch information
axenteoctavian committed Jan 31, 2024
commit bce29e1a3934e1290577703d9dffde9ccdee2388
18 changes: 11 additions & 7 deletions cmd/node/config/prefs.toml
Original file line number Diff line number Diff line change
@@ -38,17 +38,21 @@
# so that certain config values need to remain the same during upgrades.
# (for example, an Elasticsearch user wants external.toml->ElasticSearchConnector.Enabled to remain true all the time during upgrades, while the default
# configuration of the node has the false value)
# The Path indicates what value to change, while Value represents the new value in string format. The node operator must make sure
# to follow the same type of the original value (ex: uint32: "37", float32: "37.0", bool: "true")
# File represents the file name that holds the configuration. Currently, the supported files are: config.toml, external.toml, p2p.toml and enableEpochs.toml
# The Path indicates what value to change, while Value represents the new value. The node operator must make sure
# to follow the same type of the original value (ex: uint32: 37, float32: 37.0, bool: true)
# Also, the Value can be a struct (ex: { StartEpoch = 0, Version = "1.5" }) or an array (ex: [{ StartEpoch = 0, Version = "1.4" }, { StartEpoch = 1, Version = "1.5" }])
# File represents the file name that holds the configuration. Currently, the supported files are: config.toml, external.toml, p2p.toml, enableEpochs.toml and fullArchiveP2P.toml
# -------------------------------
# Un-comment and update the following section in order to enable config values overloading
# -------------------------------
# OverridableConfigTomlValues = [
# { File = "config.toml", Path = "StoragePruning.NumEpochsToKeep", Value = "4" },
# { File = "config.toml", Path = "MiniBlocksStorage.Cache.Name", Value = "MiniBlocksStorage" },
# { File = "external.toml", Path = "ElasticSearchConnector.Enabled", Value = "true" }
#]
# { File = "config.toml", Path = "StoragePruning.NumEpochsToKeep", Value = 4 },
# { File = "config.toml", Path = "MiniBlocksStorage.Cache.Name", Value = "MiniBlocksStorage" },
# { File = "external.toml", Path = "ElasticSearchConnector.Enabled", Value = true },
# { File = "external.toml", Path = "HostDriversConfig", Value = [
# { Enabled = false, URL = "127.0.0.1:22111" },
# ] },
# ]

# BlockProcessingCutoff can be used to stop processing blocks at a certain round, nonce or epoch.
# This can be useful for snapshotting different stuff and also for debugging purposes.
Loading