Jussi Mäki 33c7a1aace Implementation for the configuration management service (#3756) ... * Implementation for the configuration management service - Add configuration generation to the response of SetTimeModel - Implement the ConfigManagementService - Implement integration test into test tool This is still a draft as it has unsolved FIXMEs and it conflicts with #3744 which should go first. The main conflict is with changes to PartyAllocationResponse which cannot no longer reference "domain.PartyDetail" as we would have a cyclic dependency (participant-state contains Configuration which we point to from domain.ConfigurationEntry). The still open issues are: - Revisit PartyDetail - Naming: LedgerConfigurationService and ConfigManagementService are not talking about the same configuration and it feels confusing. - Remove duplication of ConfigurationEntry? Do we need both domain.ConfigurationEntry and ledger.store.ConfigurationEntry? Only difference is in the types of participantId and submissionId. * Address review part 1 * Fix up tests after rebase and address PR review * Post-merge fixes * Add missing config MRT checks and fixes to tests - Check config MRT in InMemoryLedger and SqlLedger - Use proper source of time in ConfigManagement - Separate out ConfigManagementServiceIT in sandbox conformance tsets * Reformat		2019-12-13 17:58:44 +00:00
..
src	Async package management (#3806)	2019-12-13 09:56:47 +01:00
BUILD.bazel	Implementation for the configuration management service (#3756)	2019-12-13 17:58:44 +00:00