Change YAML format to match upcoming agent release

EnterpriseDB · Sep 26, 2024 · 4c9a62e · 4c9a62e
1 parent bb6bfe6
commit 4c9a62e
Showing 1 changed file with 13 additions and 13 deletions.
diff --git a/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx b/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx
@@ -114,16 +114,16 @@ Entries under `databases` utilize the following format:
 
 ```yaml
 databases:
-    <database_name_1>:
-        dsn: "$DSN1"
-        tags:
-            - "<tag-one>"
-            - "<tag-two>"
-    <database_name_2>:
-        dsn: "$DSN2"
-        tags: 
-            - "<tag-one>"
-            - "<tag-two>"
+  - resource_id: "database_name_1"
+    dsn: "$DSN1"
+    tags:
+        - "<tag-one>"
+        - "<tag-two>"
+  - resource_id: "database_name_2"
+    dsn: "$DSN2"
+    tags: 
+        - "<tag-one>"
+        - "<tag-two>"
 ```
 
 Here is an example `beacon_agent.yaml` file configured for a database named `sales_reporting`:
@@ -142,11 +142,11 @@ agent:
 provider:
   onprem:
     databases: 
-      sales_reporting:
+      - resource_id: "sales_reporting"
         dsn: "$DSN"
         tags:
-            - "sales"
-            - "reports"
+          - "sales"
+          - "reports"
     host:
       resource_id: "postgresql.lan"
       tags: []