Re: [ansible-project] change of parsing of values? (in ansible.cfg)

2024-01-11 Thread Brian Coca
It should not break again, the code had 'ini' source detection broken, since it was looking for 'ini' as origin, but we set '/path/to/ansible.cfg' instead, so it was not matching. -- -- Brian Coca (he/him/yo) -- You received this message because you are subscribed to the Google Groups

Re: [ansible-project] change of parsing of values? (in ansible.cfg)

2024-01-10 Thread Adrian Sevcenco
On 08.01.2024 21:26, Brian Coca wrote: sorry, yes, that pr above broke it, this one should fix it https://github.com/ansible/ansible/pull/82388 my brain just came back from vacation and reminded me Thanks a lot for info! I closed the community.general issue with your information! I'm not

Re: [ansible-project] change of parsing of values? (in ansible.cfg)

2024-01-08 Thread Brian Coca
sorry, yes, that pr above broke it, this one should fix it https://github.com/ansible/ansible/pull/82388 my brain just came back from vacation and reminded me -- -- Brian Coca (he/him/yo) -- You received this message because you are subscribed to the Google Groups "Ansible Proje

Re: [ansible-project] change of parsing of values? (in ansible.cfg)

2024-01-08 Thread Brian Coca
Not really, only thing I can think of is this PR https://github.com/ansible/ansible/pull/79837, but ini should have kept the old behavior. -- -- Brian Coca (he/him/yo) -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe

[ansible-project] change of parsing of values? (in ansible.cfg)

2024-01-06 Thread Adrian Sevcenco
So, after updating of ansible (i do not know the versions that i had) and in the context of setting values for redis fact caching see https://github.com/ansible-collections/community.general/issues/7814 i notice that quotes are now interpreted literally instead of being evaluated... so for an empt