What is the nature and description of the request?
The customer is requesting the ability to trigger playbook executions defined within the Ansible Automation Platform (AAP) user interface (UI) directly from an external shell or command-line interface (CLI), outside the AAP UI. This functionality would allow them to programmatically initiate playbook runs without logging into the AAP web interface.

Why does the customer need this? (List the business requirements here)

• The customer wants to integrate playbook execution with other external tools and scripts that operate in a shell or CLI environment.

• Reducing dependency on the AAP UI enables faster and more automated workflows, improving operational efficiency.

• Shell-based execution provides flexibility to incorporate AAP playbooks in custom pipelines or incident response processes.

How would you like to achieve this? (List the functional requirements here)

• Allow execution of playbooks by referencing the Job Template ID or name from AAP.

• Ensure the CLI method supports passing extra variables, credentials, inventory, and other parameters just like in the AAP UI.

• Authentication should be supported via tokens or credentials securely stored or passed to the CLI.

• Output from the job (such as job status, logs) should be retrievable from the CLI to allow monitoring and integration with other systems.