# \#requirements

**URL:** https://forum.ansible.com/tag/requirements/323.md

[Latest](https://forum.ansible.com/latest.md) · [Categories](https://forum.ansible.com/categories.md) · [Tags](https://forum.ansible.com/tags.md)

---

## [AWX Source Control Type Manual Not processing requirements.yml](https://forum.ansible.com/t/awx-source-control-type-manual-not-processing-requirements-yml/44921)

<div class="topic-metadata">

**Author:** [@ky-lab\_rat](https://forum.ansible.com/u/ky-lab_rat)\
**Replies:** 0\
**Last updated:** [December 1, 2025, 4:03pm UTC](https://forum.ansible.com/t/awx-source-control-type-manual-not-processing-requirements-yml/44921 "2025-12-01T16:03:05Z")

</div>

When using manual Source Type it appears that AWX does not read/source the requirements.yml. I’ve made sure the syntax and such is correct by using checking it with ansible-galaxy. I’ve put a copy of the file in all 3 p…

---

## [galaxy.ansible.com cloudflare down awx broken](https://forum.ansible.com/t/galaxy-ansible-com-cloudflare-down-awx-broken/44857)

<div class="topic-metadata">

**Author:** [@rbooyer](https://forum.ansible.com/u/rbooyer)\
**Replies:** 8\
**Last updated:** [November 18, 2025, 8:16pm UTC](https://forum.ansible.com/t/galaxy-ansible-com-cloudflare-down-awx-broken/44857 "2025-11-18T20:16:05Z")

</div>

currently with galaxy.ansible.com down due to a Cloudflare issue in Dallas my awx project is broken as it cannot pull in anything for the requirements.yaml file. collections: name: community.general name: awx.awx I …

---

## [Serious collection requirement violation of cisco.mso: undeclared dependency on cisco.nd (which isn't part of Ansible community package)](https://forum.ansible.com/t/serious-collection-requirement-violation-of-cisco-mso-undeclared-dependency-on-cisco-nd-which-isnt-part-of-ansible-community-package/7039)

<div class="topic-metadata">

**Author:** [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Replies:** 13\
**Last updated:** [July 15, 2024, 10:01pm UTC](https://forum.ansible.com/t/serious-collection-requirement-violation-of-cisco-mso-undeclared-dependency-on-cisco-nd-which-isnt-part-of-ansible-community-package/7039 "2024-07-15T22:01:39Z")

</div>

While working on an ansible-test extension (validate-modules: reject option/alias names equal up to casing belonging to different options by felixfontein · Pull Request #83530 · ansible/ansible · GitHub) I noticed that a…

---

## [\[Vote ended on 2024-01-30\] Ansible collection inclusion requirements: remove absolute ban of \`undocumented-parameter\` ignore.txt entry](https://forum.ansible.com/t/vote-ended-on-2024-01-30-ansible-collection-inclusion-requirements-remove-absolute-ban-of-undocumented-parameter-ignore-txt-entry/3055)

<div class="topic-metadata">

**Author:** [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Replies:** 10\
**Last updated:** [January 31, 2024, 5:37pm UTC](https://forum.ansible.com/t/vote-ended-on-2024-01-30-ansible-collection-inclusion-requirements-remove-absolute-ban-of-undocumented-parameter-ignore-txt-entry/3055 "2024-01-31T17:37:46Z")

</div>

Right now the Ansible collection inclusion requirements on CI testing explicitly state that undocumented-parameter is one of the errors you MUST NOT ignore in tests/sanity/ignore-\*.txt. Some collections in Ansible violat…