Peter Broadhurst

Think both of these are a great step forwards. They match how Firefly Transaction Manager evolved, and we already took part of pattern and back-ported to a small piece of...

A few bits of background that I think are worth considering with this one. Currently in FireFly there are two related objects which represent an attempt to perform a blockchain...

In the logs, I see us go into the backend request, but never come back: ``` [2022-09-22T17:25:23.105Z] DEBUG ==> POST http://host.docker.internal:1234/walletReceiver breq=LiHKZU5S pid=1 ``` While there is room for improvement...

The lack of logging might have been a red-herring here, due to using `resty` in raw response mode for the webhooks code. I've raised #1072 to improve the logging, and...

As well as updating the code, I've done an extra update on the docs - particularly to clarify the behavior around redelivery of webhook events. The code generated docs for...

Hmmn, well actually this is more significant a change than I thought. We had been relying on a Kustomize as per the below, in order to create a nested set...

It will take a bit of work to try and form a PR proposal that meets both requirements 🤔

That is indeed the change in behavior we've seen. Before we were able to generate a sample `values.yaml` that contained a detailed set of individual config settings, which a user...

I note one previous approach to generating such end-user config we'd found was to bind an environment variable with a `valueFrom` pointing at a `ConfigMap` resource. `helmfiy` generated a unique...

I believe https://github.com/hyperledger/firefly/pull/1242 might contain a fix for this - the `namespaceInitWaiter`