Switch from Azure Postgres single server to flexible server

[giulio-giunta]

Switched from Azure Postgres single server to flexible server, removed deployment of Postgres database in pod, adjusted database connection settings

Description

Switched from Azure Postgres single server, which has reached the end of support, to Postgres flexible server, which supports new versions of Postgres.

Related Issue

"resolves #53"

Motivation and Context

Azure Postgres single server only supports older versions of Postgres, which are no longer supported by the Django version installed in the Geek Zone app.

How Has This Been Tested?

I tested by manually applying the terraform and Kubernetes templates, until I could connect the Geek Zone backend to the managed Azure Postgres database.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[sonarcloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud