ccuz

Based on idea #998 this implementation allow to run the semaphore ansible task within a prepared python virtual environment '.venv' (default naming per convention for python venv) . Note: In...

We had the same issue with Bolt. Switched using MariaDB and it got fixed. Relates to https://github.com/ansible-semaphore/semaphore/blob/develop/api/login.go#L165 and implementation of https://github.com/ansible-semaphore/semaphore/blob/develop/api/login.go#L170. It seems LDAP user get added into the database...

Log into Semaphore as Admin and delete any existing 'local' user with the same username/userid as you would expect from LDAP, as the code doesn't work with both a local...

After reading the existing login code, it may already work as HTTP Header 'Authorization bearer' is already extracted https://github.com/ansible-semaphore/semaphore/blob/f674738f54258b976265f53fe228d45f8ba7efc5/api/auth.go#L21 into a userID: "userID = token.UserID". Basically Semaphore has the concept...

I ended up creating a `hooks/post-checkout` and `hooks/post-merge` within the ansible git project: ``` #!/bin/bash echo "Git repo hook: $0" echo "Create a python venv" python3 -m .venv myproject source...

For the container runtime integration with podman: - Without podman local socket: https://github.com/containers/podman/discussions/9076 - Podman RestAPI (with local socket to podman deamon, requires podman to be installed on the system):...