Six modules take their secrets from files; the rest say precisely why not

From the survey of every env-file secret (ADR 0086, issue 041): amqp-ping,
minio, mongodb and grafana use the _FILE twin their software honours;
mesh-catalog and model-usage read DATABASE_URL_FILE (a file the mesh
templates, mounted where only the runtime reads it); grafana's secret files
belong to its own account. Two dead deliveries removed: a line nothing read
in amqp-email-forwarder, and mailu's secret.env on four containers that
never read it. The 25 exceptions that remain carry the surveyed reason —
convertible and awaiting a bed, convertible through a generated config file,
the application's own code, or not convertible.

modules/grafana/module.json

@@ -32,13 +32,6 @@
       "path": "/var/lib/grafana-module",
       "mode": "0700"
     },
-    {
-      "id": "server-env",
-      "type": "file",
-      "path": "/var/lib/grafana-module/server.env",
-      "mode": "0600",
-      "content": "GF_SECURITY_ADMIN_PASSWORD=${secret:admin}\n"
-    },
     {
       "id": "data",
       "type": "directory",
@@ -51,16 +44,16 @@
       "type": "container",
       "name": "grafana",
       "image": "grafana/grafana@sha256:f772d434e8fab0049deb2b1b30abd43342bcfca1537614aa8d36080232cf4283",
-      "env-file": [
-        "/var/lib/grafana-module/server.env"
-      ],
       "ports": [
         "3000"
       ],
       "volumes": [
-        "/services/grafana/data:/var/lib/grafana"
+        "/services/grafana/data:/var/lib/grafana",
+        "/var/lib/grafana-module/admin.secret:/run/secrets/admin:ro"
       ],
-      "secrets-in-environment": "the image reads its configuration from the environment only; converting to a file is the per-module work of issue 041"
+      "env": {
+        "GF_SECURITY_ADMIN_PASSWORD__FILE": "/run/secrets/admin"
+      }
     },
     {
       "id": "runtime-config",
@@ -122,5 +115,6 @@
         "from": "Dockerfile"
       }
     ]
-  }
+  },
+  "secrets-owner": "472:472"
 }