sonic-buildimage/files/build_templates/tacacs-config.timer

[Unit]
Description=Delays tacacs apply until SONiC has started
PartOf=tacacs-config.service
After=updategraph.service

[Timer]
OnUnitActiveSec=0 sec
OnBootSec=5min 30 sec
Unit=tacacs-config.service

[Install]
WantedBy=timers.target sonic.target sonic-delayed.target
Add service to restore TACACS from old config (#7560) Why I did it In upgrade scenarios, where config_db.json is not carry forwarded to new image, it could be left w/o TACACS credentials. Added a service to trigger 5 minutes after boot and restore TACACS, if /etc/sonic/old_config/tacacs.json is present. How I did it By adding a service, that would fire 5 mins after boot. This service apply tacacs if available. How to verify it Upgrade and watch status of tacacs.timer & tacacs.service You may create /etc/sonic/old_config/tacacs.json, with updated credentials (before 5mins after boot) and see that appears in config & persisted too. Which release branch to backport (provide reason below if selected) 201911 202006 202012 2021-06-03 22:07:17 -05:00			`[Unit]`
			`Description=Delays tacacs apply until SONiC has started`
			`PartOf=tacacs-config.service`
			`After=updategraph.service`

			`[Timer]`
			`OnUnitActiveSec=0 sec`
			`OnBootSec=5min 30 sec`
			`Unit=tacacs-config.service`

			`[Install]`
[services] Update "WantedBy=" section for tacacs-config.timer. (#11893) The timer execution may fail if triggered during a config reload (when the sonic.target is stopped). This might happen in a rare situation if config reload is executed after reboot in a small time slot (for 0 to 30 seconds) before the tacacs-config timer is triggered. To ensure that timer execution will be resumed after a config reload the WantedBy section of the systemd service is updated to describe relation to sonic.target. Signed-off-by: Oleksandr Ivantsiv <oivantsiv@nvidia.com> Signed-off-by: Oleksandr Ivantsiv <oivantsiv@nvidia.com> 2022-09-08 17:16:11 -05:00			`WantedBy=timers.target sonic.target sonic-delayed.target`