> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/pam/fr/knowledge-base/knowledge-base-articles/ansible-module.md).

# Module Ansible

Utilisez le module Ansible de Devolutions Server pour vous authentifier avec des identités d’application et récupérer les informations du serveur, les coffres et les secrets.

Ce module Ansible vous permet de vous authentifier auprès de Devolutions Server et de récupérer les informations du serveur, les coffres et les secrets.

{% hint style="info" %}
Consultez notre [GitHub](https://github.com/Devolutions/ansible-dvls) pour en savoir plus sur le module Ansible pour Devolutions Server.
{% endhint %}

### Fonctionnalités

* S'authentifier auprès de Devolutions Server à l'aide d'identités d’application.
* Récupérer les informations du serveur, les listes de coffres ou des secrets spécifiques.
* Prise en charge flexible des secrets statiques ou de la récupération de tous les secrets d'un coffre.

### Exigences

* Ansible 2.18
* Bibliothèque Python `requests`
* Une identité d’application Devolutions Server (à créer à `{your-dvls-url}/administration/applications`).
  * L'application doit avoir les permissions nécessaires pour récupérer les secrets souhaités.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/pam/fr/knowledge-base/knowledge-base-articles/ansible-module.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.