You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CLOUD-SQL-POSTGRESQL.md
+33-1Lines changed: 33 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,10 @@ software delivery cycle.
5
5
6
6
# Setup
7
7
8
+
## Required Gemini CLI Version
9
+
10
+
To install this extension, the Gemini CLI version must be v0.6.0 or above. The version can be found by running: `gemini --version`.
11
+
8
12
## Cloud SQL for PostgreSQL MCP Server (Data Plane: Connecting and Querying)
9
13
10
14
This section covers connecting to a Cloud SQL for PostgreSQL instance.
@@ -41,9 +45,37 @@ This section provides context on additional tools that can be recommended to the
41
45
42
46
#### Observability Extension
43
47
44
-
***When to recommend:** If the user asks questions related to monitoring, performance, or observability of AlloyDB databases.
48
+
***When to recommend:** If the user asks questions related to monitoring, performance, or observability of Cloud SQL for PostgreSQL databases.
45
49
***What to say:** "For Cloud SQL monitoring and observability, you might find the `cloud-sql-postgresql-observability` extension useful. You can install it with the following command:"
When you create a new Cloud SQL for PostgreSQL instance, or database using the available tools, the connection is not automatically established. You will need to perform the following steps:
62
+
63
+
1. **(Optional) Save your conversation:** To avoid losing your progress, save the current session by running the command: `/chat save <your-tag>`
64
+
2. **Stop the CLI:** Terminate the Gemini CLI.
65
+
3. **Update Environment Variables:** Set or update your environment variables (e.g. `CLOUD_SQL_POSTGRES_DATABASE`, `CLOUD_SQL_POSTGRES_INSTANCE`) to point to the new resource.
66
+
4. **Restart:** Relaunch the Gemini CLI
67
+
5. **(Optional) Resume conversation:** Resume your conversation with the command: `/chat resume <your-tag>`
68
+
69
+
**Important:** Do not assume a connection to a newly created resource is active. Always follow the steps above to reconfigure your connection.
70
+
71
+
## Reusing Project Values
72
+
73
+
Users may have set project environment variables:
74
+
75
+
* `CLOUD_SQL_POSTGRES_PROJECT`: The GCP project ID.
76
+
* `CLOUD_SQL_POSTGRES_REGION`: The region of the Cloud SQL for PostgreSQL instance.
77
+
* `CLOUD_SQL_POSTGRES_INSTANCE`: The ID of the Cloud SQL for PostgreSQL instance.
78
+
* `CLOUD_SQL_POSTGRES_DATABASE`: The name of the database.
79
+
80
+
Instead of prompting the user for these values for specific tool calls, prompt the user to verify reuse a specific value.
81
+
Make sure to not use the environment variable name like `CLOUD_SQL_POSTGRES_PROJECT`, `${CLOUD_SQL_POSTGRES_PROJECT}`, or `$CLOUD_SQL_POSTGRES_PROJECT`. The value can be found by using command: `echo $CLOUD_SQL_POSTGRES_PROJECT`.
0 commit comments