PostgreSQL State Store: Add separate metadata options for secret connection string details

[alicejgibbons]

Describe the feature

Today in PostgreSQL v2 state there is only the option to provide the connection string as a single metadata property. Eg. "host=localhost user=postgres password=example port=5432 connect_timeout=10 database=my_db"

This forces some secret values (password) to be contained in the same metadata property as potentially non-secret values (host, port, db, etc.) The ask is to allow separation of sensitive values (like passwords) from non-sensitive connection info via metadata options. This would allow more streamlined property update of passwords while keeping other values easy readable.

Specifically it would be sufficient to provide only the following "potentially sensitive" values as separate metadata values while still allowing the rest of the values to be provided in the existing connection string metadata property:

• host
• database
• user
• password
• sslrootcert

Obviously if connection string is provided these are not required and vice versa.

Release Note

RELEASE NOTE: Add separate metadata options for connection string details