@Viacheslav - how does the bug around which you were working manifest itself? I just pulled the 1.1.6 sources and built from that repo using the same command as the Jenkinsfile. Happy to test for whatever condition was being fixed in the local build

In T4533#126598, @c-po wrote:

In T4533#126578, @Viacheslav wrote:

It is operator level, that shouldn’t have permission for configurations. Only basic diagnostics (op-mode)

Operator mode is no longer supported in VyOS 1.4

Even if so - we should still try to "support" it somehow for the upcoming future when there is a true secure op-mode again.

Could you please add a new Cmnd_Alias vor VRF to /etc/sudoers.d/vyos and allow it for the %operator group?

ip vrf exec requires the CAP_SYS_ADMIN capability which somehow is more or less equal to root.

It seems working:

● telegraf.service - The plugin-driven server agent for reporting metrics into InfluxDB
     Loaded: loaded (/lib/systemd/system/telegraf.service; disabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/telegraf.service.d
             └─10-override.conf
     Active: active (running) since Mon 2022-08-29 12:51:47 EEST; 1min 7s ago
       Docs: https://github.com/influxdata/telegraf
   Main PID: 6740 (telegraf)
      Tasks: 9 (limit: 9409)
     Memory: 49.7M
        CPU: 836ms
     CGroup: /system.slice/telegraf.service
             └─vrf
               └─foo
                 └─6740 /usr/bin/telegraf --config /run/telegraf/telegraf.conf --config-directory /etc/telegraf/telegraf.d --pidfile /run/telegraf/telegraf.pid

@syncer We'll add/merge it to 1.3.3 (We discussed it and agree to add it after 1.3.2 release)

@Viacheslav is this backported and present in 1.3.2?

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