There is an ongoing discussion in the background between the maintainers for more then a year how to get rid of the hw-id node in general and do such a detection once during initial boot.

And similar example, using same interfaces and host, but instead of GRE tunnel, using a Wireguard site to site tunnel:

Example of using flowtables on mater interfaces, and communication between a local host that is on a VLAN (vlan eth2.22 and host 10.22.22.222), and a remote host that is reachable through a GRE tunnel (tunnel established using interface eth0):

By looking at this and the documentation, I do not see any proofs that flowtables support any encapsulation except VLAN and PPPOE.

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

PR https://github.com/vyos/vyos-build/pull/594
PR https://github.com/vyos/vyos-1x/pull/3412

Can you try with newver version?
New fixes were applied.
You can check this tasks:
https://vyos.dev/T6269
https://vyos.dev/T6191

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

Ok, that makes sense. Still need to place the tag.

Not all targets have username/password
For example for the future "location"

set system config-management commit-archive aws authentication access-key
set system config-management commit-archive aws authentication secret-key
set system config-management commit-archive aws bucket <my-bucket-name>
set system config-management commit-archive aws path '/'

This way, predefined targets are more preferred.

The format I started playing with looks like this:

set system config-management commit-archive 1 username 'xxx'
set system config-management commit-archive 1 password 'xxx'
set system config-management commit-archive 1 scheme 'scp'
set system config-management commit-archive 1 location '192.0.2.1/backup'

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

Adding additional PR to add bonding.py to op-mode-standardized.json: https://github.com/vyos/vyos-1x/pull/3408

What about this format?
We still have named/predefined targets (scp|ftp|sftp|http|https) and <name> as tag

set system config-management commit-archive target scp <name> authentication username 'xxx'
set system config-management commit-archive target scp <name> authentication password 'xxx'
set system config-management commit-archive target scp <name> server '192.0.2.1'
set system config-management commit-archive target scp <name> path '/'

https://github.com/vyos/vyos-1x/pull/3405

https://github.com/vyos/vyos-1x/pull/3405

https://github.com/vyos/vyos-build/pull/591

https://github.com/vyos/vyos-build/pull/591

need configuration index too or maybe name
so we can have several destinations for same protocol

I already looked a bit into it. What complicates it is the old location is a multi and one can add a list of locations.

Should be fixed after rewriting commit-archive T6304

NETNS was removed from the 1.4 series the other day so hopefully that feature can be worked on for 1.5 since its needed:

What you're trying to achieve seems to be a derivate of https://www.wireguard.com/netns/

How was this configuration achieved? Or is it manually crafted?

Closed in https://github.com/vyos/vyos-build/pull/586

It is probably a commit in progress during this time of execution, so the file is locked by another commit.
@dex Can you send to syslog anu message or do any other commands not related to configure?

Will be available in the next rolling release.