Bradley A. Thornton
Bradley A. Thornton
disallow the default "item" var from propagating outside a single task, even if the initial implementation was just for "import" tasks this would be a good start
@ajinkyau Can you look into this? ping me if more info is needed
example of a sidecar https://github.com/ansible-collections/ansible.windows/blob/main/plugins/modules/async_status.yml
We're talking about this! I'm not sure it will go into the navigator code base because we need this for a few projects but I think where we are headed...
I need to dig deeper, but this is as far as I got so far, we call `run_command_async` from ansible runner passing the /tmp/ansible-navigatorxxxxx as private_data_dir ``` {'container_image': 'ghcr.io/ansible/crea...ee:v0.17.0', 'process_isolation_executable':...
Any of that would need to be done by runner.... Navigator doesn't craft the command line. Will look at the runner code later tonight.
``` ansible-navigator run site.yml --eei test-ee --pp never --co="-uroot" --la false ``` this works fine for podman but not for docker ``` ansible-navigator run site.yml --eei test-ee --pp never --co="--userns=keep-id"...
it appears userns was once in runner: https://github.com/ansible/ansible-runner/pull/759
I went ahead and merged the navigator PR and released version 3.3.1, the tests were passing and I had good success with it locally. I still find myself thinking container...
@max06 If it doesn't help with navigator, maybe it will with another project of yours. I've been doing some early testing with container in container leveraging some of what the...