Now, svcusr-sls2hla should be allowed to execute sudo shellbox ...
Log onto the target machine as root (or with admin privileges) and create a dedicated file under /etc/sudoers.d/:
`sudo visudo -f /etc/sudoers.d/svcusr-sls2hla`
Add a line granting your deployment SSH user (`svcusr-sls2hla`) permission to run specific binaries without a password prompt:
`svcusr-sls2hla ALL=(ALL) NOPASSWD: sudo shellbox status, sudo shellox ...` (is `... sudo shellbox` enough?)
Now, `svcusr-sls2hla` should be allowed to execute `sudo shellbox ...`
labrec_b
added this to the Setup CI/CD runners milestone 2026-07-29 11:03:02 +02:00
labrec_b
changed title from Setup ioc host dev/prod runners on `sls-vserv- to Setup ioc host dev/prod runners on `sls-vserv-bd-01(-dev)`2026-07-29 11:03:46 +02:00
labrec_b
added this to the Benjamin Labrecque project 2026-07-29 13:37:24 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Log onto the target machine as root (or with admin privileges) and create a dedicated file under /etc/sudoers.d/:
sudo visudo -f /etc/sudoers.d/svcusr-sls2hlaAdd a line granting your deployment SSH user (
svcusr-sls2hla) permission to run specific binaries without a password prompt:svcusr-sls2hla ALL=(ALL) NOPASSWD: sudo shellbox status, sudo shellox ...(is... sudo shellboxenough?)Now,
svcusr-sls2hlashould be allowed to executesudo shellbox ...Setup ioc host dev/prod runners on `sls-vserv-to Setup ioc host dev/prod runners on `sls-vserv-bd-01(-dev)`