Hi! 👋
I followed your tutorial to use pgAdmin as a database explorer for a PostgreSQL instance in SAP BTP, and it works perfectly at first.
However, I’ve noticed that every time my Cloud Foundry app is rescheduled (for example, after an update, restart, or platform maintenance), the server connection in pgAdmin is removed.
This means I have to manually reconfigure the connection each time, which is quite inconvenient.
Steps to reproduce
- Deploy the app following your tutorial
- Configure pgAdmin and connect to the PostgreSQL instance
- Trigger a rescheduling (for example, cf restart APP_NAME)
- Open pgAdmin again → the connection is gone
Expected behavior
- The server connection should persist across restarts/rescheduling events.
Question
Is there a way to persist pgAdmin configuration (server connections, users, etc.) across app reschedules?
Maybe by using a persistent volume, service binding, or storing configuration in a mounted directory?
Thanks a lot for your work on this! 🙏
Hi! 👋
I followed your tutorial to use pgAdmin as a database explorer for a PostgreSQL instance in SAP BTP, and it works perfectly at first.
However, I’ve noticed that every time my Cloud Foundry app is rescheduled (for example, after an update, restart, or platform maintenance), the server connection in pgAdmin is removed.
This means I have to manually reconfigure the connection each time, which is quite inconvenient.
Steps to reproduce
Expected behavior
Question
Is there a way to persist pgAdmin configuration (server connections, users, etc.) across app reschedules?
Maybe by using a persistent volume, service binding, or storing configuration in a mounted directory?
Thanks a lot for your work on this! 🙏