feat: support list based gateway env vars

openclaw_assistant/config.yaml

@@ -104,22 +104,18 @@ options:
   # minimal: suppress repetitive HA health-check and polling requests (default)
   nginx_log_level: minimal
 
-  # Environment variables to pass to the gateway as a YAML map
-  # These variables are exported to the gateway process at startup
-  # Examples:
-  #   API keys:
-  #     OPENAI_API_KEY: "sk-abc123"
-  #     ANTHROPIC_API_KEY: "claude-key"
-  #   Service URLs:
-  #     SERVICE_URL: "https://api.example.com"
-  #     LOG_LEVEL: "debug"
-  #   Feature flags:
-  #     FEATURE_FLAG_X: "1"
-  #     FEATURE_FLAG_Y: "0"
+  # Environment variables to pass to the gateway process at startup.
+  # Format: list of objects with name/value fields.
+  # Example:
+  #   gateway_env_vars:
+  #     - name: OPENAI_API_KEY
+  #       value: "sk-abc123"
+  #     - name: LOG_LEVEL
+  #       value: "debug"
   # Reserved keys are blocked to protect runtime/security
   # (e.g. PATH, HOME, NODE_OPTIONS, NODE_PATH, OPENCLAW_*, proxy vars).
   # Limits: max 50 variables, max key length 255 chars, max value length 10000 chars
-  gateway_env_vars: {}
+  gateway_env_vars: []
 
 
 schema:
@@ -144,5 +140,7 @@ schema:
   gateway_trusted_proxies: str?
   enable_openai_api: bool?
   force_ipv4_dns: bool?
-  gateway_env_vars: map(str)?
+  gateway_env_vars:
+    - name: "match(^[A-Z_][A-Z0-9_]*$)"
+      value: str
   nginx_log_level: list(full|minimal)?