[fixes #145] Bug: Database connection issue when using postgres-operator

[mwallschlaeger]

Description

fixes bug when using default database configuration with postgres-operator.

Type of Change

Please select the relevant option:

• [x] Bug fix
• [ ] New feature
• [ ] Documentation update
• [ ] Refactoring
• [ ] Other (please describe)

Related Issue

If there is an existing issue related to this pull request, please reference it here.

closes #145

Checklist

Please ensure that your pull request meets the following requirements:

• The pull request is limited to one type (docs, feature, bug fix, etc.)
• The pull request is as small as possible. Consider opening multiple pull requests instead of one large one.
• The feature or bug fix has been discussed and documented in an issue beforehand.

Additional Notes

Any additional information or context regarding the pull request can be provided here.

Thank you for creating this pull request

[AlexGacon]

@mwallschlaeger using always the same name implies that you cannot ship all the secrets in one file. Is it not possible to have a different name for each password ?

[mwallschlaeger]

@AlexGacon ok now I remember fully how postgres integration is implemented currently. Three different scenarios:

1. using postgres-operator and doen't furhter care about database passwords
2. using external_postgres and provide hostname, port and passwords via:
   • external_postgres.hostname , external_postgres.port, external_postgres.secret.postgres_password ...
3. using external_postgres and provide credentials via a single secret file containing:
   • postgres_password, geonode_password, geodata_password

Currently scenario 1. broken. My fix breaks scenario 3., so i will do some furhter sepration to support the 3. usecase.

[AlexGacon]

Looking good to me.