Ability to Use Postgres as a Backing Store for VSecM Safe

[v0lkan]

Ability to Use Postgres as a Backing Store for VSecM Safe

Description

This pull request provides the option for VMware Secrets Manager to use Postgres as a backing store instead of the default "persistent volume."

Changes

• Added a new backing store type "postgres"
• When backing store is configured to be "postgres" any attempt to read from and write to disk panicks.
• Ability to configure VSecM Safe for postgres usage
• Configuration update is dynamic (no need to restart VSecM Safe)

To configure, a command like the following will be needed:

k exec $S -n vsecm-system -- safe \
-w vsecm-safe \
-s '{"config":{"backingStore":"postgres","dataSourceName":"postgresql://postgres:Hx07Cvjf4Q@my-postgres-postgresql.default.svc.cluster.local:5432/postgres?sslmode=disable"}}'

Code Quality

• I have followed the coding standards for this project.
• I have performed a self-review of my code.
• My code is well-commented, particularly in areas that may be difficult
  to understand.

Additional Comments

This is an initial stab at this feature.
Follow-up issues will

• Address any TODO: item in the comments.
• Create documentation
• Update unit and integration tests.
• Flexibility in configuration (for example, ability to change the name of the database table to be used)

Checklist

Before you submit this PR, please make sure:

• You have read the contributing guidelines and
  especially the test policy.
• You have thoroughly tested your changes.
• You have followed all the contributing guidelines for this project.
• You understand and agree that your contributions will be publicly available
  under the project's license.

By submitting this pull request, you confirm that my contribution is made under
the terms of the project's license and that you have the authority to grant
these rights.

---

Thank you for your contribution to VMware Secrets Manager
🐢⚡️!