> 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/da/knowledge-base/knowledge-base-articles/ansible-module.md).

# Ansible-modul

Brug Ansible-modulet til Devolutions Server til at godkende med programidentiteter og hente serveroplysninger, bokse og hemmeligheder.

Dette Ansible-modul lader Dem godkende med Devolutions Server og hente serveroplysninger, bokse og hemmeligheder.

{% hint style="info" %}
Se vores [GitHub](https://github.com/Devolutions/ansible-dvls) for at få mere at vide om Ansible-modulet til Devolutions Server.
{% endhint %}

### Funktioner

* Godkend med Devolutions Server ved hjælp af programidentiteter.
* Hent serveroplysninger, bokslister eller specifikke hemmeligheder.
* Fleksibel understøttelse af statiske hemmeligheder eller hentning af alle hemmeligheder i en boks.

### Krav

* Ansible 2.18
* Python-biblioteket `requests`
* En programidentitet til Devolutions Server (opret den på `{your-dvls-url}/administration/applications`).
  * Programmet skal have tilladelser til at hente de ønskede hemmeligheder.


---

# 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/da/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.