61 lines
2.9 KiB
ReStructuredText
61 lines
2.9 KiB
ReStructuredText
Variables as Code
|
||
==================
|
||
|
||
|
||
Definition
|
||
--------------
|
||
|
||
.. glossary::
|
||
|
||
VaC
|
||
|
||
VaC stands for **Variables as Code**, it is the practice of managing configuration variables the same way you treat source code.
|
||
|
||
It is a concept that extends the Infrastructure as Code (IaC) philosophy to the management of configuration variables, secrets, and environment-specific settings.
|
||
More precisely, this extends Configuration as Code (CaC) principles.
|
||
|
||
The idea is to treat variables — not just infrastructure or configuration — as version-controlled, declarative, and automated code rather than manual, static, or hardcoded values.
|
||
|
||
With growing complexity of the infrastructure, it is difficult to manage all the variables.
|
||
Due to more and more available variables required to set up the infrastructure,
|
||
it became quite annoying to hand the necessary variables to where they are actually used
|
||
and even more annoying to add new variables.
|
||
|
||
Variables can be redundant and sometimes are defined on several places.
|
||
|
||
Ansible collections
|
||
-------------------------
|
||
|
||
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.
|
||
|
||
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.
|
||
|
||
Variables as Code with Rougail
|
||
-----------------------------------
|
||
|
||
For this, we thought of a solution and came up with a concept of managing all our variables as a code called VaC (Variables as Code).
|
||
|
||
Often when we talk about :term:`VaC` (or CaC) we think of the different environments (Development, Staging, Production).
|
||
|
||
With Rougail, this question does not arise. Essentially, Rougail manages this with user data.
|
||
Here we're talking about sharing variables between projects.
|
||
|
||
Furthermore, using a tool like Rougail allows you to use variables with different IaC deployment solutions without having to redefine those variables.
|
||
It can be said that Rougail allows you to use variables not only between projects but also between tools.
|
||
|
||
To do this, we need typed variable definitions with defaults and validation.
|
||
|
||
Once defined, variables must be able to:
|
||
|
||
- provide useful information to the operator to make their choices
|
||
- load user values from differents sources
|
||
- validate the context
|
||
- display and archive the final values in a readable format
|
||
- allow other applications to use these variables
|
||
|
||
|