compose, validator: Fix restoration from dump (#387)

Author: giner

apps/app/src/test/scala/org/lfdecentralizedtrust/splice/integration/tests/DockerComposeValidatorFrontendIntegrationTest.scala

@@ -191,7 +191,7 @@ class DockerComposeValidatorFrontendIntegrationTest
       "recovering from identities dump",
       Seq(
         "-i",
-        backupsDir.toAbsolutePath.toString,
+        identities.toAbsolutePath.toString,
         "-P",
         "da-composeValidator-13",
       ),

cluster/compose/validator/compose-restore-from-id.yaml

@@ -12,4 +12,4 @@ services:
           ADDITIONAL_CONFIG_MIGRATE_VALIDATOR_PARTY=
             canton.validator-apps.validator_backend.migrate-validator-party.scan.admin-api.url = "${SCAN_ADDRESS}"
     volumes:
-      - ${VALIDATOR_PARTICIPANT_IDENTITIES_DUMP}:/participant-bootstrapping-dump
+      - ${VALIDATOR_PARTICIPANT_IDENTITIES_DUMP}:/participant-bootstrapping-dump/identities.json

docs/src/release_notes.rst

@@ -32,6 +32,14 @@ Upcoming
 
   - Fix an issue where the mediator sometimes got stuck after initialization and required a restart to recover.
 
+- Validator
+
+  - docker-compose, breaking: Restoration from identities dump requires to
+    specify path to `identities.json` and not directory containing it. This is
+    consistent with the :ref:`documented
+    <validator_disaster_recovery-docker-compose-deployment>` behavior.  See
+    `#387 <https://github.com/hyperledger-labs/splice/pull/387>`_
+
 0.4.1
 -----
 

docs/src/validator_operator/validator_disaster_recovery.rst

@@ -107,6 +107,8 @@ While doing so, please note the following:
     :start-after: PARTICIPANT_BOOTSTRAP_MIGRATE_TO_NEW_PARTICIPANT_START
     :end-before: PARTICIPANT_BOOTSTRAP_MIGRATE_TO_NEW_PARTICIPANT_END
 
+.. _validator_disaster_recovery-docker-compose-deployment:
+
 Docker-Compose Deployment
 ^^^^^^^^^^^^^^^^^^^^^^^^^