Kurtis Van Gent f630965937 feat!: consolidate "x-postgres-generic" tools to "postgres-sql" tool (#43) ...

This PR introduces the following breaking change: The
`alloydb-pg-generic`, `cloud-sql-pg-generic`, and
`postgres-generic-tool` have been replaced by the `postgres-sql` tool,
which works with all 3 Postgres sources.

If you were using of the the previous tools, you will need to update it
as follows:
```diff
example_tool:
-    kind: cloud-sql-pg-generic
+    kind: postgres-sql
     source: my-cloud-sql-pg-instance
     description: some description
        statement: |
            SELECT * FROM SQL_STATEMENT;
        parameters:
        - name: country
          type: string
          description: some description
```

I'm proposing this change for the following reasons:
1. It provides greater flexibility between postgres-compatible sources
-- you can change between "postgres" and "alloydb-postgres" without
issue
2. The name "postgres-sql" is more clear that "postgres-generic" -- it
indicates it's a tool that runs SQL on the source
3. It's easier for us to maintain feature compatibility across a single
"postgres-sql" tool

2024-11-01 16:17:18 -07:00

..

api_test.go

chore: refactor sources/tools each into their own package (#42)

2024-11-01 16:44:13 -06:00

api.go

fix: handle content-type correctly (#33)

2024-10-29 20:00:22 +00:00

config.go

feat!: consolidate "x-postgres-generic" tools to "postgres-sql" tool (#43)

2024-11-01 16:17:18 -07:00

server_test.go

chore: refactor sources/tools each into their own package (#42)

2024-11-01 16:44:13 -06:00

server.go

chore: refactor sources/tools each into their own package (#42)

2024-11-01 16:44:13 -06:00