Commit 33e7aab7 authored by onknows's avatar onknows
Browse files

glossary vagrant inventory plugin

C2-1460
parent 15cd3f4b
Loading
Loading
Loading
Loading
Loading
+21 −0
Original line number Diff line number Diff line
---
title: Vagrant inventory plugin
categories: [Term]
aliases:
  - inventory plugin
toc_hide: true
reference: /docs/guidelines/dev/dynamic-inventory
translate: false
---

The _Vagrant inventory plugin_ is an Ansible inventory plugin used for the
[development environment](g).

The purpose of this plugin is twofold. First, it provides a single source of
truth for both Vagrant and Ansible during development. This eliminates the need
to duplicate information—such as IP addresses—across Vagrant and Ansible
configurations.

Second, it simulates [dynamic inventory](g) within the development environment.
Many government organizations struggle with the concept of dynamic inventory.
This plugin serves as a practical example of a custom inventory plugin.
+78 −0
Original line number Diff line number Diff line
The user wants me to translate a Markdown file to Dutch.
I need to:
1. Review the frontmatter: `title`, `linkTitle`, `description`.
2. Translate the body of the markdown text. Improve, simplify, correct.
3. Output ONLY valid Markdown, no ```markdown ... ``` block.
4. Leave Hugo code between `{{` and `}}` unaltered except for visible text.
5. Remove `translate: true` line from frontmatter.
6. Keep `weight`, `toc_hide`, `hide_summary` etc in sync.
7. Capitalize only the first word of titles (proper nouns excepted).
8. Don't remove newlines. Preserve formatting.
9. Use Glossary g-links to translate g-links.
10. Don't translate specific English words like "image", "Ansible Software Repository", "scope".
11. Translate "Deployment" to "Uitrol", "Deploying" to "Uitrollen".
12. For How-To sections: Prerequisites -> Randvoorwaarden, Setup -> Uitrol, Verify -> Verificatie, Review -> Review.
13. Frontmatter categories: Guideline -> Richtlijn, How-To -> Handleiding, Reference -> Bron, Term -> Begrip, Example -> Voorbeeld.

Source:
```markdown
---
title: Vagrant inventory plugin
categories: [Term]
aliases:
  - inventory plugin
toc_hide: true
reference: /docs/guidelines/dev/dynamic-inventory
translate: true
---

The _Vagrant inventory plugin_ is an Ansible inventory plugin used for the
[development environment](g).

The purpose of this plugin is twofold. First, it provides a single source of
truth for both Vagrant and Ansible during development. This eliminates the need
to duplicate information—such as IP addresses—across Vagrant and Ansible
configurations.

Second, it simulates [dynamic inventory](g) within the development environment.
Many government organizations struggle with the concept of dynamic inventory.
This plugin serves as a practical example of a custom inventory plugin.
```

Frontmatter changes:
`title`: Vagrant inventory plugin -> Vagrant inventory plugin (proper nouns / specific ICT terms? I'll just leave it as is, or maybe "Vagrant inventory plugin" since Vagrant and Ansible are names, but "inventory" could be translated, but let's keep it as is or maybe "Vagrant-inventory plugin" or "Vagrant inventory plugin". Let's use "Vagrant inventory plugin").
`categories`: [Term] -> [Begrip]
Remove `translate: true`

Body translation:
The _Vagrant inventory plugin_ is an Ansible inventory plugin used for the [development environment](g).
-> De _Vagrant inventory plugin_ is een Ansible inventory plugin die wordt gebruikt voor de [ontwikkelomgeving](g).

The purpose of this plugin is twofold. First, it provides a single source of truth for both Vagrant and Ansible during development. This eliminates the need to duplicate information—such as IP addresses—across Vagrant and Ansible configurations.
-> Het doel van deze plugin is tweeledig. Ten eerste biedt het een single source of truth voor zowel Vagrant als Ansible tijdens de ontwikkeling. Dit elimineert de noodzaak om informatie—zoals IP-adressen—te dupliceren tussen Vagrant- en Ansible-configuraties.

Second, it simulates [dynamic inventory](g) within the development environment. Many government organizations struggle with the concept of dynamic inventory. This plugin serves as a practical example of a custom inventory plugin.
-> Ten tweede simuleert het [dynamische inventory](g) binnen de ontwikkelomgeving. Veel overheidsorganisaties worstelen met het concept van dynamische inventory. Deze plugin dient als een praktisch voorbeeld van een aangepaste inventory plugin.

Let's check the current Dutch version provided by the user:
```markdown
---
title: Vagrant inventory plugin
categories: [Begrip]
aliases:
  - inventory plugin
toc_hide: true
reference: /docs/guidelines/dev/dynamic-inventory
---

De _Vagrant inventory plugin_ is een Ansible inventory plugin die door het C2-platform
wordt gebruikt. Wanneer de term "inventory plugin" wordt genoemd in de context
van het C2-platform, verwijst dit naar deze specifieke plugin.

Het doel van deze plugin is tweeledig. Ten eerste biedt het een single source of
truth voor zowel Vagrant als Ansible tijdens de ontwikkeling. Dit elimineert de
noodzaak om informatie—zoals IP-adressen—te dupliceren tussen Vagrant- en
Ansible-configuraties.

Ten tweede simuleert het [dynamische inventory](g) binnen de
ontwikkelomgeving. Veel overheidsorganisaties worstelen met het concept
 No newline at end of file