{# Reusable AAP deployment form. Required context: deploy_target – "skill" or "collection" deploy_name – skill name or collection FQCN collection_fqcn – (optional) collection FQCN for EE warning deploy_action – POST URL (e.g. /api/aap/deploy-skill) aap_configured – bool, injected by middleware #}
{% if aap_configured %} ✅ AAP Controller connected {% else %} Production deployment path {% endif %}
{% if aap_configured %}
Deploying this {% if deploy_target == "collection" %}collection{% else %}skill{% endif %} will create
{% if deploy_target == "collection" %}one Job Template per module skill{% else %}a Job Template{% endif %}
in your AAP Controller{% if jt_name_prefix is defined and jt_name_prefix %}, each named with prefix {{ jt_name_prefix }}{% endif %}.
AnsibleClaw does not launch jobs; execution is for AAP administrators in the Controller.
Playbooks are pushed to the selected Project’s Git repo and the project is synced before the Job Template is created.
The playbook path is project-relative (as you define for that project); AnsibleClaw does not re-check it against the Controller after sync.
{% else %}
Ansible Automation Platform (AAP) is the recommended way to run generated skills in production.
Visit the AAP settings page to configure your controller connection.
{% endif %}