Parameterize cardano-testnet on config yaml files

[Jimbo4350]

Currently cardano-testnet relies on a hardcoded configuration yaml file: https://github.com/input-output-hk/cardano-node/blob/91cc07a9c085373085391be130fc1aff96a2c8fc/cardano-testnet/src/Testnet/Cardano.hs#L225

And then updates the yaml file in an ad hoc fashion: https://github.com/input-output-hk/cardano-node/blob/91cc07a9c085373085391be130fc1aff96a2c8fc/cardano-testnet/src/Testnet/Cardano.hs#L280

This makes it more challenging to vary settings in the configuration per test (e.g if you wanted to output JSON logs instead of plain text logging, test incorrect configuration settings etc).

Allowing the specification of the configuration yaml file for all the nodes in question would be a good start. The eventual aim would be to modify the cardano-testnet executable to allow specification of a single yaml file for all nodes or individual yaml files for each node.

• It it now possible to set the configurational YAML file for each property independently
• The cardano-testnet executable allows the specification of independent YAML files for each node (with sensible defaults if none are specified)

[newhoggy]

#3727

[newhoggy]

Heads up that recent aeson upgrade to version 2 in cardano-node will make updating plutus-apps more challenging because dependencies in that repo rely on version 1.

[smelc]

#6148 made it possible to configure all the nodes using the same configuration file.

Now remains to make it possible to have each node receive a different configuration file.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.