Splice 0.6.10
Added support for secretOverrides for Helm charts. This allows node operators to inject raw configuration strings for an external secret manager. To use this, you must have the corresponding mutating webhook installed…
- A newer release in the 0.6 line: Splice 0.6.14
- Newest Splice: Splice 0.9.4
Open the release notes (opens in a new tab)docs.canton.network
-
Deployment
-
Helm
-
Added support for
secretOverridesfor Helm charts. This allows node operators to inject raw configuration strings for an external secret manager. To use this, you must have the corresponding mutating webhook installed in your cluster to dynamically resolve raw string references at runtime. -
Added support for injecting custom
serviceAccountNameinto deployments. Note that Splice Helm charts do not create Service Account resources; operators must separately deploy and annotate their own service accounts.
-
Added support for
-
Helm
-
PostgreSQL Data Checksums
- PostgreSQL data checksums are now
enabled by default for all PostgreSQL databases created by Splice. This applies to the
in-cluster Postgres Helm chart (
splice-postgres) and the Docker-Compose based deployments (SV, validator and LocalNet). Data checksums help detect on-disk data corruption early.
- PostgreSQL data checksums are now
enabled by default for all PostgreSQL databases created by Splice. This applies to the
in-cluster Postgres Helm chart (
-
Splice nodes now perform a best-effort check at startup and log a
WARNif PostgreSQL data checksums are not enabled on their backing database. This check never fails startup. -
Database instance locking
- Splice apps now take a PostgreSQL instance lock on startup so
that only one instance runs against a given database at a time, guarding against data
corruption from an accidentally duplicated app. Enabled by default
(
instanceLockEnabled = true); set it tofalseonly if you deliberately point multiple apps at one shared database.
- Splice apps now take a PostgreSQL instance lock on startup so
that only one instance runs against a given database at a time, guarding against data
corruption from an accidentally duplicated app. Enabled by default
(
-
Validator, sv and scan app
- Support passing client-id and secret through Http Basic Authentication instead of in the request body. For backwards compatibility this is disabled by default.
To enable it set an environment variable
ADDITIONAL_CONFIG_HTTP_BASIC_AUTH=canton.validator-apps.validator_backend.participant-client.ledger-api.auth-config.http-basic-auth = true.
- Support passing client-id and secret through Http Basic Authentication instead of in the request body. For backwards compatibility this is disabled by default.
To enable it set an environment variable
-
SV app
-
Now logs a warning if a mismatch is detected in
Confirmationfor the following actions, as these are submitted by automations and no disagreement is expected:CRARC_MiningRound_Archive,CRARC_MiningRound_StartIssuingandCRARC_StartProcessingRewardsV2 - The governance Vote History is now ordered by effective date rather than ingestion order.
- The Set DSO Rules governance form now accepts an empty (null) ACS commitment reconciliation interval instead of requiring a value.
- Config-change diffs for DSO Rules and Amulet configuration proposals now show correct Daml maps serialized to JSON.
- The proposal form to unfeature an app now clearly indicates when there are no featured apps available to unfeature, instead of showing an empty selector.
-
Now logs a warning if a mismatch is detected in