Summary
The Galaxy server list configuration options section at https://docs.ansible.com/projects/ansible/latest/collections_guide/collections_installing.html mentions validate_certs which seems to work with ansible-core 2.20.
If the option is fully supported then it would probably be a good idea to mention it in the main config document as well: https://docs.ansible.com/projects/ansible/latest/reference_appendices/config.html
Issue Type
Documentation Report
Component Name
galaxy
Ansible Version
Configuration
OS / Environment
N/A
Additional Information
This is an often needed option that should be worth mentioning the config option main page. There were also few others, at least client_id and auth_url missing as well. Not sure would be warranted to add those as well. Perhaps yes as some users might only read the main config options page.
Code of Conduct
Summary
The Galaxy server list configuration options section at https://docs.ansible.com/projects/ansible/latest/collections_guide/collections_installing.html mentions validate_certs which seems to work with ansible-core 2.20.
If the option is fully supported then it would probably be a good idea to mention it in the main config document as well: https://docs.ansible.com/projects/ansible/latest/reference_appendices/config.html
Issue Type
Documentation Report
Component Name
galaxy
Ansible Version
2.20Configuration
N/AOS / Environment
N/A
Additional Information
This is an often needed option that should be worth mentioning the config option main page. There were also few others, at least client_id and auth_url missing as well. Not sure would be warranted to add those as well. Perhaps yes as some users might only read the main config options page.
Code of Conduct