Jimi is an automation first platform designed from the ground by IT and Cyber Security. Automation first means that the usual product limitations are removed opening the possibilities of automation to all aspects of IT. Jimi features a rich no-code user interface creating a single pane of glass that effortlessly integrate your existing tools unlocking new possibilities and enabling cross functional automation.
Ultimately would be nice to run the services in individual containers which would then enable them to be used in container orchestration tools such as K8s, k3s, swarm etc
Batfish can query network device configs, calculate routing paths, verify access/ACLs and generally assert whether parts of the network will do X or Y. It should be useful before applying changes to give a heads up on what may need configuring (as in firewalls along traced path) or to check a configuration before deployment to validate it.
Now that the container version is almost working, would be nice to see how it runs in K3S Kubernetes and Rancher
So far I have pushed the images to a local insecure harbor registry
When rebuilding the containers during testing (docker-compose build && docker-compose up) it seems that the passwords stored in the flows are no longer decryptable due to some kind of key change or system id change possibly?
Need to look into how the decryption keys can persist.