V7.20beta [testing] is released!

[fischerdouglas]

@Amm0

Perhaps in the slew of /container feature, you should consider adding “events” to container some

/container add on-change={ :put "$[get $.id name] changed from $from to $to" }

or broken out to on-stop= on-stopping= on-error-state= on=start= on=stop= … – just quite a few of them, and you can just provide the “state” (ideally both from and to) as variable to one generic script handler.

Sometime ago I suggested a more “event-based” triggering feature for RouterOS scripting.

Suggestion: Hooks to Scripts on /routing/filter/rule actions

It colud cover all the already existing script events, like:

• /ppp/profile/ “on-up” and “on-down”
• /ip/dhcp-server/ “lease-script”
• /ipv6/dhcp-server/ “binding-script”
• /tool/netwatch/ “up-script” and “down-script”

And also would allow almos everything like those suggestions that were already done at the thread:

• BGP Flowspec
• Route Leak Between VRFs
• QoS policy propagation using BGP (QPPB)

Also would avoid the need of some stupid pooling log that are triggered by time-scheduled script.
An example? Do something whne some user logs-in via any protocol.
I use that for some “fail2ban” tool.

@Amm0

Right now even with all the good changes in /container, it’s still a shitshow to script container, properly, without either a lot of script to poll and check states, or error-prone :delay.

Based on your description of what you need in container scripting… To me seems like a hook-based / event-based scripts trigger (in this case related to container) wolud solve your problem.