-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connecting databases between apps #669
Comments
Hey I believe both of those applications should have support for that built in, is the issue network access to the app db? |
My apologies. Yes, how would it be in terms of networking within the Plural Cluster. |
We default to creating the cluster within its own vpc, so if those app dbs are located in a private network within their own vpc you might need to peer the two: https://docs.plural.sh/operations/network-configuration#configuring-vpc-peering |
Yes, what I'm trying to accomplish is connecting one app database to another app using the Postgres connection parameters. For example, if I deposit information con HASURA default database how do I get the connection parameters for to connect Postgres to other app (for example Metabase to analyze them)? Sorry if my statement was unclear and for the inconvenience. |
For example, this tutorial provides information about how to connect to a db using the console. https://docs.plural.sh/operations/managing-applications/connect-application-db But, is there a way to get the connection parameters to the app database? I mean, user, password, ip within the vpc. |
sorry @roicort i lost track of this issue, the application db is cluster local so assuming the process connecting to it is in the cluster, it would be available at |
What content is missing
Is there a way to connect the db of one app to another app?
For example connecting an app db to AirByte to create a ETL
or another app db to Metabase to view analytics.
Message from the maintainers:
Are you looking for the same documentation content? Give it a 👍. We factor engagement into prioritization.
The text was updated successfully, but these errors were encountered: