feat(config): Configure GLPI from json config files

!1

docs/projects/nfc_glpi/config_from_code.md

@@ -0,0 +1,74 @@
+---
+title: Config as code
+description: How to use No Fuss Computings Ansible role to configure GLPI from configuration as code.
+date: 2023-07-28
+template: project.html
+about: https://gitlab.com/nofusscomputing/projects/ansible/nfc_glpi
+---
+
+To configure GLPI using this role, the config/settings are saved as json files. The workflow to create the json files, is to (preferably within a test environment) make the required setting changes in GLPI using the GUI. one the changes have been made, conduct an API `GET` query to GLPI for the item you changed. The JSON body that is returned, is placed within the Config file (detailed below) under path `.body`. You must however, remove any fields that are not required, for example dynamic fields (fields that update themselves or are auto created) for example date fields.
+
+
+
+## Config files Example
+
+Each tab provides an example of the JSON file layout, including any additional variables. Any variable listed at path `.` that are empty strings, you would complete with the items name as it is exactly within GLPI. These fields are used to fetch the itm_id of the field by name. this enables having the config saved in a more human readable format. For example, for the field `entities_id` you would complete it as `"entities_id": "My entity name"`.
+
+=== "AuthLDAP"
+
+    ``` json title="example.json" linenums="1
+    {
+      "api_path": "AuthLDAP",
+      "body": {
+        // JSON from API Query
+      }
+    }
+    ```
+=== "Entity"
+
+    ``` json title="example.json" linenums="1
+    {
+      "api_path": "Entity",
+      "entities_id": "",
+      "body": {
+        // JSON from API Query
+      }
+    }
+    ```
+
+=== "ITILCategory"
+
+    ``` json title="example.json" linenums="1
+    {
+      "api_path": "ITILCategory",
+      "users_id": "",
+      "itilcategories_id": "",
+      "entities_id": "",
+      "tickettemplates_id_demand": "",
+      "body": {
+        // JSON from API Query
+      }
+    }
+    ```
+
+=== "Profile"
+
+    ``` json title="example.json" linenums="1
+    {
+      "api_path": "Profile",
+      "body": {
+        // JSON from API Query
+      }
+    }
+    ```
+
+With the config files structured as per the examples, within your playbook(s), load the json files in a list of json objects using variable `glpi_config_as_code_json`
+
+example
+
+``` yaml title="my_vars.yaml" linenums="1
+glpi_config_as_code_json:
+  - "{{ lookup('file', '/workdir/files/glpi/ITILCategory-new-ldap-user.json') | from_json }}"
+  - "{{ lookup('file', '/workdir/files/glpi/LDAPAuth-local_ldap.json') | from_json }}"
+
+```

docs/projects/nfc_glpi/index.md

@@ -1,5 +1,5 @@
 ---
-title: Ansible Role nfc_glpi
+title: nfc_glpi - Ansible Role
 description: How to use No Fuss Computings Ansible role to manage GLPI from configuration as code.
 date: 2023-07-28
 template: project.html
@@ -13,6 +13,7 @@ This Ansible role is designed to manage GLPI specifically installation and confi
 
 - install GLPI using our [docker container](https://gitlab.com/nofusscomputing/projects/docker-glpi)
 
+- [Configure using Config from Code](config_from_code.md)
 
 ## Default Variables