Raphaël Vinot
Raphaël Vinot
If you pass a key `breakOnDuplicate` directly in the object, it will automatically trigger the feature: https://github.com/MISP/PyMISP/commit/5b97b7d0158906cd0f646a7273a3ca5b1828cd15 This test case calls `add_object`, but the same code is used on update,...
It definitely deserves to be exposed on the update method. The other place where it should be mentioned is the `MISPEvent.add_object` method: adding/updating a complete event with objects having that...
So break_on_duplicate at object level for update_object doesn't work for now.
WiP pull request: https://github.com/MISP/PyMISP/pull/709
I had do to the same to get it work. @eduardohenriquearnold thank you!
it is definitely unexpected from PyMISP side, `self.misp.get_object_template(o['template_uuid'])` doesn't expect `None` there. I'm not sure how you can get to the point where an object you get from MISP doesn't...
Either that, or when you export the event from MISP, as it is not tied to a known template, it cannot fill the field. If that's the case, it should...
it seems that `-s` would do the trick. I've been doing a lot of messing around and I don't have the problem anymore, so I'm unsure in which conditions that...
that's very possible. I use your docker there: https://github.com/MISP/dockerized_training_environment Where I setup 20+ instances, with sync links and sharing groups. There is a lot going on, including some black magic,...
oh yeah, nginx was definitely not starting