Import/export functionality for runtime.yaml
There should be a feature to import/export the runtime.yaml file. This is useful if we want to have multiple deployments.
Hi @m4rb3n ,
thanks for your message.
You can simply export the runtime.yaml by using /etc/intelmq/runtime.yaml directly.
Import is a more complicated process. That includes making a diff from the old to the new configuration. Clearing all queues of removed bots. Starting all new bots, reloading bots with changed configuration.
Hey @sebix thanks for the feedback. I am asking for this functionality because we are running intelmq in kubernetes and we do not have an easy access to the file system, so an export function in the UI would be nice.
I understand that importing is a more complicated process but it would be nice if we had that functionality because if we want to deploy another intelmq and copy the same workflow that we are already using we have to access the filesystem of the old deployment and copy the runtime.yaml. Then, we have to access the filesystem of the new deployment and copy the runtime.yaml to there. It is a tedious process.
Great to hear IntelMQ is running in K8s :)
I understand the feature request. As you mentioned the UI, I guess you wish for an API call (not a command line program). The initial message wasn't clear about that.
I gonna leave this issue open in case someone has the resources to implement it. We welcome your contributions to IntelMQ as well. Furthermore, I take the liberty of referring to https://intelmq.readthedocs.io/en/latest/user/support.html#assistance
Hey @m4rb3n
Awesome that you managed to run IntelMQ in K8s. I'd be very interested in the following topics:
- Do you run everything inside one pod?
- Did you build your own image?
- Have you encountered any problems running in K8s?
Regards,
Hey @waldbauer-certat, sorry for the late response. In my deployment I have two different pods, one for the frontend and other for the backend. The deployment was fairly simple and it is running very well. One of the limitation that I have right now is with the logging. Each Bot has its own logs but the logs do not have any rotation policy so we end up having large log files.