Configure autorefresh after change in security groups provider openstack

[cronosy]

Greetings team.
Today I come with the next question. I would like to improve my end user experience, reducing the time to show the changes in security group rules or CRUD operations. For instance, in my current situation, my end users update a security group and take at least 20 minutes (the next provider scan ) to reflect the change. I wondered if I could avoid the scan entirely the provider and instead just scan network manager (openstack case).

kind regards.

[Fryguy]

If there are events, those can be configured to kick a refresh, so for example when the security group is created, we can catch that event and have it do a targeted refresh immediately. I thought we had all of those events pre-configured, but maybe we missed it. cc @agrare

[agrare]

I see a number of event handlers related to security groups in our event content: https://github.com/ManageIQ/manageiq-content/tree/master/content/automate/ManageIQ/System/Event/EmsEvent/OpenStack.class/

security_group.create.end.yaml
security_group.delete.end.yaml
security_group_rule.create.end.yaml
security_group_rule.delete.end.yaml
security_group_rule.update.end.yaml
security_group.update.end.yaml

Can you post the event type that is caught by the Event Catcher when you have a user update a security group? E.g. this is one of the events that we have security_group.update.end maybe newer versions of OpenStack have different event names.