zulip/puppet/zulip_ops/templates/teleport.service.template.erb

[Unit]
Description=Teleport <%= @part %> Service
After=network.target

[Service]
Type=simple
Restart=on-failure
EnvironmentFile=-/etc/default/teleport_<%= @part %>
ExecStart=/usr/local/bin/teleport start --pid-file=/run/teleport_<%= @part %>.pid --config=/etc/teleport_<%= @part %>.yaml
ExecReload=/bin/kill -HUP $MAINPID
PIDFile=/run/teleport_<%= @part %>.pid
LimitNOFILE=524288

[Install]
WantedBy=multi-user.target
puppet: Switch teleport to running under systemd, not supervisord. There is no reason that the base node access method should be run under supervisor, which exists primarily to give access to the `zulip` user to restart its managed services. This access is unnecessary for Teleport, and also causes unwanted restarts of Teleport services when the `supervisor` base configuration changes. Additionally, supervisor does not support the in-place upgrade process that Teleport uses, as it replaces its core process with a new one. Switch to installing a systemd configuration file (as generated by `teleport install systemd`) for each part of Teleport, customized to pass a `--config` path. As such, we explicitly disable the `teleport` service provided by the package. The supervisor process is shut down by dint of no longer installing the file, which purges it from the managed directory, and reloads Supervisor to pick up the removed service. 2023-03-15 15:37:54 +01:00			`[Unit]`
			`Description=Teleport <%= @part %> Service`
			`After=network.target`

			`[Service]`
			`Type=simple`
			`Restart=on-failure`
			`EnvironmentFile=-/etc/default/teleport_<%= @part %>`
			`ExecStart=/usr/local/bin/teleport start --pid-file=/run/teleport_<%= @part %>.pid --config=/etc/teleport_<%= @part %>.yaml`
			`ExecReload=/bin/kill -HUP $MAINPID`
			`PIDFile=/run/teleport_<%= @part %>.pid`
			`LimitNOFILE=524288`

			`[Install]`
			`WantedBy=multi-user.target`