Replies: 3 comments 2 replies
|
You want key: ansible_user value:itansible as extra vars(cli equivalent -e ansible_user=itansible). If you want to use Environment vars it is also possible: the key is ANSIBLE_REMOTE_USER in that case |
0 replies
|
I too have set |
0 replies
|
Hello, You should |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Issue
Not sure if it's a bug or it's me that was unable to find anything about it, but basically, is there a way to change the user used for the initial SSH connections?
Semaphore is installed with a dedicated user "semaphore".
The remote servers are configured to use a specific user for ansible task "itansible".
Seems that, even with "ansible_user=itansible" set in environment variables the SSH connection is initiated as semaphore@ which fails.
Seems that Semaphore is ignoring the environment variable?
Or it's me setting wrongly?
From my understanding, the "Environment variables" should be something you could add inside the "ansible.cfg", is that right?
I've made also that test, editing "ansible.cfg" and that worked as expected, the SSH connection was initiated as itansible, while Semaphore still tried to connect as "semaphore@"
Impact
Ansible (task execution)
Installation method
Package
Database
Postgres
Browser
No response
Semaphore Version
2.15.4-8e8d81c-1753268666
Ansible Version
Logs & errors
No response
Manual installation - system information
Running on Ubuntu 22.04 (5.15.0-144-generic)
Configuration
No response
Additional information
There seems it was a similar question asked few years ago #382 but it's not a real solution (IMHO)
All reactions