apenella comments

Results 56 comments of


                                            apenella

Set -v (VerboseV) not working

Hi @prakasa1904! Version v2.0.1 solves the issue with the [String](https://github.com/apenella/go-ansible/blob/master/pkg/playbook/ansiblePlaybookOptions.go#L561) method, which returned the verbose flags incorrectly. However, as I mentioned, when `go-ansible` executes a command, it uses the [GenerateCommandOptions](https://github.com/apenella/go-ansible/blob/master/pkg/playbook/ansiblePlaybookOptions.go#L276)...

Set -v (VerboseV) not working

I will close this issue as no further assistance is required.

when i run job using go-ansible in dockerized environment as microservice it block all traffic to my existing other docker and the system become inaccessible

Hi @MohamedKHALILRouissi! I am not aware of anyone else experiencing this issue. `go-ansible` doesn't handle container or networking operations, it just executes Ansible commands. Therefore, I believe the root cause...

when i run job using go-ansible in dockerized environment as microservice it block all traffic to my existing other docker and the system become inaccessible

@MohamedKHALILRouissi could your issue be related to [that](https://github.com/apenella/go-ansible?tab=readme-ov-file#considerations) in some way?

when i run job using go-ansible in dockerized environment as microservice it block all traffic to my existing other docker and the system become inaccessible

@MohamedKHALILRouissi, is there any update on this issue? Have you identified the cause of the described behaviour? Thanks!

when i run job using go-ansible in dockerized environment as microservice it block all traffic to my existing other docker and the system become inaccessible

@MohamedKHALILRouissi I close the issue due to the lack of activity. If you have any questions, please, feel free open a new issue.