Modifications apportées aux fichiers goss.yaml concernant l'agent Zabbix, et ajout de preuves au README.

goss/goss_ap31-prod.yaml

@@ -12,10 +12,10 @@ package:
         installed: true
         versions:
             - 10.1.6-1+deb12u2
-    zabbix-agent:
+    zabbix-agent2:
         installed: true
         versions:
-            - 1:6.0.14+dfsg-1+b1
+            - 1:7.0.5-1+debian12
 service:
     mariadb:
         enabled: true
@@ -32,7 +32,7 @@ service:
     tomcat10:
         enabled: true
         running: true
-    zabbix-agent:
+    zabbix-agent2:
         enabled: true
         running: true
 user:
@@ -66,4 +66,4 @@ http:
         no-follow-redirects: false
         timeout: 5000
         body:
-          - Apache Tomcat # Le motif que Goss cherche
+            - Apache Tomcat

goss/goss_ap31-test.yaml

@@ -16,10 +16,10 @@ package:
         installed: true
         versions:
             - 10.1.6-1+deb12u2
-    zabbix-agent:
+    zabbix-agent2:
         installed: true
         versions:
-            - 1:6.0.14+dfsg-1+b1
+            - 1:7.0.5-1+debian12
 service:
     mariadb:
         enabled: true
@@ -36,7 +36,7 @@ service:
     tomcat10:
         enabled: true
         running: true
-    zabbix-agent:
+    zabbix-agent2:
         enabled: true
         running: true
 user:
@@ -66,6 +66,25 @@ interface:
             - 172.16.0.101/24
             - fe80::be24:11ff:fe8d:7f30/64
         mtu: 1500
+http:
+    http://172.16.0.101:8080:
+        status: 200
+        allow-insecure: false
+        no-follow-redirects: false
+        timeout: 5000
+        body:
+            - Apache Tomcat
+
+            - 10.121.38.7
+        timeout: 500
+        server: 10.121.38.8
+interface:
+    eth0:
+        exists: true
+        addrs:
+            - 172.16.0.101/24
+            - fe80::be24:11ff:fe8d:7f30/64
+        mtu: 1500
 http:
     http://172.16.0.101:8080:
         status: 200