R.I.Pienaar

Interesting, certainly possible but would need to think about it, the configuration system is pretty overloaded with features already :) I tend to solve that with project directories since your...

The 2nd problem is as a result of new behavior in the NATS Server introduced in https://github.com/nats-io/nats-server/commit/e6479dafd2fc2d21b9b7899d22503aeafc51d33b so I need to do some bug fix around that The first, need...

While the basic issue is fixed, we need to ensure `plugin.choria.network.gateway_name` is set for leafnodes in the puppet model, we might do some fqdn rand based default.

Not been able to reproduce this, added some debug to help narrow it down

Added a basic service registry structure to the gossip system - its really R&D stuff so wont document till much later.

Agree and this is a known issue. We use the NATS go package that does not let us update names like that :( I will have a chat with the...

In your exact scenario I could perhaps improve the situation - nats can learn about new hosts on its own. So when you expanded the cluster to 2 nodes the...

@binford2k well, it is pretty awful ... :) I could probably retain the exact same argument parsing on this as a backward option?

thank you, looks good, please rebase to main

I am sorry this fell under the radar while I was on holiday, would you mind rebasing and I will get this in for you.