When working with multiple clients and projects, what practices have you all found that work well for documenting system architecture and the corresponding gateway configuration? Outside of multiple Word docs, which I don't prefer, I haven't found a great system yet to highlight high-level configuration strategies and patterns, while also going into detail where needed when it comes to the gateway configuration in scale-out and other system architectures.
2 Likes
I'm interested in this as well... What would be cool is a Gateway Configuration report (that you can export as a PDF or some other format) that includes all of the gateway configurations that were committed (only non-default values), possibly the Network diagram if the GAN is used, and other useful data. Then you can look at the report, or, if its in a specific YAML-like syntax instead of PDF, do a diff between gateways to see their differences in configuration.
I think this would be easy(ier) to do in 8.3 - maybe that's a feature they will ship with. I would certainly use something like that.
If you make your v8.3 gateway a git repo, I would expect git diff to be useful.
2 Likes