The package name for Ansible changes with the current development version.
It seems like pip lets me install Ansible 2.9 and 2.10 at the same time...
bash-4.4# pip3 show ansible
Name: ansible
Version: 2.9.7
Summary: Radically simple IT automation
Home-page: https://ansible.com/
Author: Ansible, I
You want the awx-project email, not this one.
And check your server logs for a traceback that happened around the time of
observing this, and share those details please. Thanks!
Alan
github: AlanCoding
On Fri, May 22, 2020 at 1:55 PM Nasir Nasir
wrote:
> [image: awx 500 error.PNG]
> Hi i am g
Matt,
I think there is valid stuff in what you're saying. Let me write out a
formula:
cd ~/Documents/test
git clone https://github.com/ansible-collections/community.aws.git
ansible-galaxy collection build
rm -rf ~/.ansible/collections/ansible_collections/community/aws/
ansible-galaxy collecti
Gotcha, I had not read close enough. Your fix looks correct.
I proposed a fix on the ansible-test side. Both are valid in my book, and
your discovery argues strongly that this should be a failure (as opposed to
either a traceback or a pass).
https://github.com/ansible/ansible/pull/70507
Thanks.
The call pattern I'd suggest for ansible-inventory would be like
ansible-inventory -i my_inventory.yml --list --export
With the export option, group_vars should show under the group. I don't
understand the rest of your problem about expecting vars from module_utils,
but I hope this gets you close
quot; and I am interested in finding a more generic approach instead
> of this workaround with split after a certain text that can be changed in
> time.
>
> Regards,
> Alex
>
>
> joi, 3 octombrie 2019, 16:02:49 UTC+3, Alan Rominger a scris:
>>
>> The call pattern I'd
Tower saves the inventory in the database that it gets from the
ansible-inventory command. To the best of my memory, ansible-inventory does
an ordered JSON dump. We later take it back out of the database for the job
run (at which point I really don't think the JSON dump is ordered), the
ordering is
First, copy the .py file for the callback plugin from the Ansible source
code to an empty local directory. That file is apparently
`ansible/lib/ansible/plugins/callback/mail.py` in your case.
Modify the 2 Ansible config settings related to the callback plugins
https://github.com/ansible/ansible/b
Hi Tony,
There is an email list for the AWX project specifically, and the question
would be better asked there.
Templating from user-provided values is specifically disabled by the
server, by marking those as unsafe with the Ansible YAML constructor. There
is a setting available to control exactl
If you convert it to a collection you can use relative imports. I am in a
very similar situation to you with the PYTHONPATH manipulation for testing.
https://github.com/ansible/awx/blob/a93b1aa3395651f01b39a03a6f122d3bdad99897/Makefile#L411
I put the root of the collection project (it's in a fold
10 matches
Mail list logo
