feat(deployment): add PostgREST deployment for query API #392
Conversation
- Add PostgREST deployment, service, and mapping configurations - Configure route /query-postgrest for PostgREST API - Use existing query-api-database-connection secret - Set PGRST_DB_ANON_ROLE to s_query (may need adjustment after deployment) Resolves Greenstand#386
|
Please verify that s_query is the correct PGRST_DB_ANON_ROLE |
|
Great! How do you test the things? Run it locally? How do you handle the debase access on your side? |
|
I tested locally using Docker Compose with a test PostgreSQL database. I didn't have access to the production database, so I couldn't verify the actual role name. I made a trees table to test and verified the PostgREST endpoints worked correctly. The Kubernetes YAML configuration also matches the current setup and should be correct as well. The s_query role name was inferred from the codebase pattern
I don't have access to the database to test this fully but it should be okay once in prod I can test to make sure it works as expected. |
| value: "public" | ||
| - name: PGRST_DB_ANON_ROLE | ||
| value: "s_query" | ||
| - name: PGRST_OPENAPI_SERVER_PROXY_URI |
There was a problem hiding this comment.
How do we handle password here? We use sealed db connection/credentials here: https://github.com/Greenstand/treetracker-query-api/blob/main/deployment/base/database-connection-sealed-secret.yaml
2 participants
Resolves #386