Closed Josua-SR closed 2 years ago
totally agree with @Josua-SR point of view on CREATEDB permissions being completely unnecessary for startup operation,if database already exists.
Thanks for all your contributions! This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
/unstale
I'm having the exact same issue.
running into the same issue. Is there any documentation of how to set up the permissions on database side, if using a shared (between applications) database server and not wasting ressources (separate daemon in memory, backup and monitoring procedures) for another mysql/mariadb instance? expected behaviour:
Thanks for all your contributions! This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Description
Steps to reproduce
Expected behavior: Portus happily uses its database
Actual behavior: Portus drops then database, and tries to create it again. Which will fail because it hasn't been assigned CREATEDB permissions - which arguably are completely unnecessary for operation.
Log:
Deployment information
Deployment method:
Kubernetes - but writing the yaml manually based on the opensuse/portus container.
Configuration:
No special configuration, apart from choosing to use postgres.
Portus version: opensuse/portus:2.5