[MaxFreedomPollard]

scripts/setup.sh is meant to install user-defined Galaxy collections and roles from config/requirements.yml. docs/deepops/configuration.md documents that file, and config.example/requirements.yml ships a template for it. The block that installs it is guarded by a check for a different file name:

if [ -d "${CONFIG_DIR}" ] && [ -f "${CONFIG_DIR}/requirement.yml" ] ; then
    cd "${CONFIG_DIR}"
    as_user ansible-galaxy collection install ... -r "requirements.yml"
    as_user ansible-galaxy role install ... -r "requirements.yml"
fi

config/requirement.yml never exists, so the block is always skipped and anything listed in config/requirements.yml is never installed. Playbooks that use those custom collections or roles then fail with a role-not-found or collection-not-found error. The typo came in with e4991dd, which added the existence check.

This PR changes the check to requirements.yml, the file the block already installs from.

Testing

With a config/ directory copied from config.example, the condition on master evaluates false (requirement.yml is absent), so the install is skipped. With this change it evaluates true and the two ansible-galaxy ... -r requirements.yml commands run. bash -n scripts/setup.sh passes. I did not run the full setup.sh on a provisioning host.

🤖 Generated with Claude Code

[dholt]

thanks!