{# 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 #}

Deploy to AAP

{% 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 %}. Playbooks are automatically pushed to the selected Project's git repo and synced before the Job Template is created. {% 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 %}

{% if aap_configured %}
{% if deploy_target == "skill" %} {% elif deploy_target == "collection" %} {% endif %} {% if collection_fqcn %} {% endif %} {# Job Template Name (skill only) #} {% if deploy_target == "skill" %}
Created in AAP as {% if jt_name_prefix is defined and jt_name_prefix %}{{ jt_name_prefix }}{% endif %}{{ deploy_name | replace('_', '-') }} (change prefix on the AAP settings page).
{% endif %} {# Project #}
The playbook will be pushed to this Project's git repo automatically. Ensure AnsibleClaw has write access (SSH key or HTTPS credentials).
{# Playbook Path #}
{% if deploy_target == "skill" %} {% else %} {% endif %}
{# Execution Environment #}
{% if collection_fqcn %} Ensure the selected EE includes {{ collection_fqcn }} {% endif %}
{# Inventory #}
{# Credential #}
{% endif %}
{% if aap_configured %} {% endif %}