-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change default Interpreter #2
Comments
Hi, |
@speed47 Do you have time to look into this issue? |
speed47
pushed a commit
that referenced
this issue
Apr 4, 2022
Sorry about the delay! Can you try with the current main branch? We've just merged #8 that references |
wilfriedroset
pushed a commit
to wilfriedroset/the-bastion-ansible-wrapper
that referenced
this issue
Aug 30, 2022
wilfriedroset
added a commit
that referenced
this issue
Apr 26, 2024
Compared to the Vanilla Ansible, Mitogen calls `sshwrapper.py` differently. This imply a different parsing to extract the options, host and command. Moreover, Mitogen does not passes the `remote_user` therefore we must set as well `BASTION_ANSIBLE_REMOTE_USER` env var. Apart from setting the `BASTION_ANSIBLE_REMOTE_USER` the wrapper works for both vanilla and mitogen connection. Users should refer to mitogen to learn about the installation process. The following commit has been tested with: * Test case #1 * Mitogen 0.3.7 * Ansible 210.8 * Python 3.9.2 * Debian 11.9 * Test case #2 * Mitogen 0.3.7 * Ansible 2.16.6 * Python 3.12 Signed-off-by: Wilfried Roset <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Today, i found time to test the wrapper in our development environment. After some cups of coffee and some ice, runs ansible in combination with The Bastion. Thanks again for the plugin!
I noticed zwei little things:
pyhton
als default interpreter. In the system requierments did you write Python 3. I had to create a symlink for the wrapper to work. Wouldn't it be better to change the interpreter to pyhton3?The text was updated successfully, but these errors were encountered: