pgbouncer user password change should not require verifier

[philrhurst]

Checklist:

• Have you added an explanation of what your changes do and why you'd like them to be included?
• Have you updated or added documentation for the change, as applicable?
• Have you tested your changes on all related environments with successful results, as applicable?
  • Have you added automated tests?

Type of Changes:

• New feature
• Bug fix
• Documentation
• Testing enhancement
• Other

What is the current behavior (link to any open issues here)?

Currently, it is not possible to clear the verifier for the _crunchypgbouncer Secret and only change the password.

What is the new behavior (if this is a feature change)?

• Breaking change (fix or feature that would cause existing functionality to change)

The new behavior mirrors what is possible for the ccp_monitoring user. The verifier can be cleared and the password change. CPK will provide the SCRAM verifier.

Other Information:

[andrewlecuyer]

@philrhurst any thoughts on an integration test to verify this change?

For instance, I do see some existing tests out there to verify the proper contents of the the PgBouncer Secret:

postgres-operator/internal/pgbouncer/reconcile_test.go

Line 52 in 740400d

func TestSecret(t *testing.T) {

Maybe this test can be expanded (or a similar test created, etc.) to cover the functionality you've implemented?

[philrhurst]

I've added a test. Let me know what you think.