> For the complete documentation index, see [llms.txt](https://manageiq.gitbook.io/mastering-cloudforms-automation-addendum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manageiq.gitbook.io/mastering-cloudforms-automation-addendum/embedded_ansible.md).

# Embedded Ansible

The most significant new Automate feature introduced in CloudForms 4.5 (ManageIQ *Fine*) was the embedded Ansible automation engine, and this has been significantly enhanced in the CloudForms 4.6 (ManageIQ *Gaprindashvili*) release.

This section describes the capabilities of Embedded Ansible in CloudForms 4.6 and ManageIQ *Gaprindashvili*.

The section contains 11 chapters:

* Introduction to Embedded Ansible
* Ansible Playbook Services
* Playbook Service Provision and Retirement State Machines
* Running an Ansible Playbook Service Non-Interactively
* Running a Playbook Service from a Button
* ManageIQ Ansible Modules
* Ansible Playbook Methods
* Calling a Playbook Method from the VM Provision State Machine
* Using Cloud Credentials
* Embedded Ansible Objects
* Troubleshooting


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://manageiq.gitbook.io/mastering-cloudforms-automation-addendum/embedded_ansible.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
