Agree with @Viacheslav and @GurliGebis comments above.

I agree, without it, you end up repeating yourself alot, with the established, related and invalid rules.
As long as they are applied before the zone specific rules (which is how I guess it used to work), it makes sense.

There are different commands

vyos@r1:~$ show bgp neighbors 192.168.122.14 advertised-routes 
% No such neighbor or address family
vyos@r1:~$ 
vyos@r1:~$ show ip  bgp neighbors 192.168.122.14 advertised-routes 
vyos@r1:~$

Should we return global state policy?
It was useful.

Tested in VyOS 1.4-rolling-202311100309:

Tested in VyOS 1.4-rolling-202311100309
Configs:
Node-1

Backport to 1.4 has conflicts https://github.com/vyos/vyos-1x/pull/2533

PR:
https://github.com/vyos/vyos-1x/pull/2532

@Viacheslav
I missed running git pull on my ansible execution node. Works as it should. Thank you!

A fix that changes the behavior back to it was https://github.com/vyos/vyos-1x/pull/2527

PR for bridge: https://github.com/vyos/vyos-1x/pull/2528

Works fine

$ curl -k --location --request POST 'https://192.168.122.11/reboot'   --form data='{"op": "reboot", "path": ["now"]}'   --form key='foo'
{"success": true, "data": "Warning: there are unsaved configuration changes!\nRun 'save' command if you do not want to lose those changes after reboot/shutdown.\n\n", "error": null}

Tested on VyOS 1.4-rolling-202311100309:

Tested in VyOS 1.4-rolling-202311100309:
The configuration:

Tested in VyOS 1.4-rolling-202311100309
The configuration:
VyOS:

@a.apostoliuk will be available in the next rolling release.