Fork the repo vyos-1x do your changes and create a PR, there are several open PR's for example https://github.com/vyos/vyos-1x/pulls
Refer to the task number T7511 in the commit message and PR header.

Thanks @red55
Would you like to create a PR to fix this?

Probably another task, but nice to have reset all connections soft in and soft out

vyos@r14:~$ reset ip bgp all 
Possible completions:
  <Enter>               Execute the current command

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

In T7474#225365, @badger42 wrote:

I am not a developer, so not sure how to implement this. This is a request for new functionality.

There is a repo for VRRP https://github.com/acassen/keepalived that we use
So it it necessary to understand how it looks like natively for keeplived before it can be implemented

We have a bug after this commit https://vyos.dev/T7497

PR
https://github.com/vyos/vyos-build/pull/968
https://github.com/vyos/vyos-build/pull/969

Send a real example from keepalived if you know how to implement this

You should use policy route
it is not cisco

Will it not do what you want?

set firewall ipv4 prerouting raw default-action 'accept'
set firewall ipv4 prerouting raw rule 10 action 'notrack'
set firewall ipv4 prerouting raw rule 10 source address '192.0.2.0/24'

Add example for rsyslog
It is not cisco

It does not like this regex https://github.com/vyos/vyos-1x/blob/0801bc6c2dd155f40fd22c64f873a01e8be25c9f/interface-definitions/service_snmp.xml.in#L16

@a.hajiyev Check the latest rolling as a fix was added resently https://github.com/vyos/vyos-1x/pull/4500

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

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

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

This way we will expect the set of commands from both sites to reproduce.
If there will be incorrect config settings as in example you provided, the task will be closed as invalid. We do not provide support via forge and will not say you what to change. There is a forum for these questions.

I attached config tests and smoketests (the most of routing protocols fail)

At the moment (during internal tests), some config tests cannot pass: