From d92fd177a84c0fd01d0cdf6931ef2d82e8514723 Mon Sep 17 00:00:00 2001 From: gwen Date: Fri, 5 Jun 2026 16:57:41 +0200 Subject: [PATCH] docs(concepts-vac): proofreading --- docs/concepts.rst | 14 ++++++++------ docs/vac.rst | 5 +++-- 2 files changed, 11 insertions(+), 8 deletions(-) diff --git a/docs/concepts.rst b/docs/concepts.rst index 60ef0c3ed..493f1b926 100644 --- a/docs/concepts.rst +++ b/docs/concepts.rst @@ -345,6 +345,14 @@ The properties can be defined permanently or according to the result of a calcul There is two main properties. +The lifespan of the variables +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +A picture is worth a thousand words: + +.. image:: images/dessin.png + + Hidden variable ~~~~~~~~~~~~~~~ @@ -400,9 +408,3 @@ This property is generally used dynamically to remove access to the variable dep - - disabled - mandatory -The lifespan of the variables ------------------------------- - -A picture is worth a thousand words: - -.. image:: images/dessin.png diff --git a/docs/vac.rst b/docs/vac.rst index 69dc29b5b..2fcf22bdc 100644 --- a/docs/vac.rst +++ b/docs/vac.rst @@ -23,14 +23,15 @@ and even more annoying to add new variables. Variables can be redundant and sometimes are defined on several places. -Ansible collections -------------------------- +Reusable and shareable variables +------------------------------------ A typical example is the management of Ansible collections. Currently, when you distribute an Ansible collection, you distribute the recipes that allow you to deploy a component, the default values ​​for certain variables, and possibly variable validation. However, you don't share the variable declarations. Therefore, each user would have to rewrite the user documentation, define the global context themselves, and so on. It is therefore the user's responsibility to maintain the consistency of the variables with these given problems. +With Rougail, the collection maintainer can do this work himself and everyone will benefit. And we're not even talking about managing variables in a multi-project context. It is often necessary to recreate the same variables with the same constraints over and over again between different projects.