stable/postgresql broken after 2.0.0 chart release

[troytop]

This change: helm/charts@7f1e47c#diff-55277ba53f205867d3498bc5c67e178bL13

...from PR 8004 breaks postgresql in minibroker because postgresPassword is now postgresqlPassword.

The service instance is still created, but when you try to bind it to an application (in CF) you get errors like:

Unexpected Response
Response code: 502
CC code:       0
CC error code: 
Request ID:    e2128dfa-ce26-43f6-6aa5-b3145dcf002a::f43a701a-f8df-4e06-9355-5b000c8df052
Description:   {
  "description": "Service broker error: unable to bind instance 1cdb13b8-2588-4f4d-8352-fe2fdb643e00: postgres-password not found in secret keys",
  "error_code": "CF-ServiceBrokerBadResponse",
  "code": 10001,
  "http": {
    "uri": "http://minibroker-minibroker.minibroker.svc.cluster.local/v2/service_instances/1cdb13b8-2588-4f4d-8352-fe2fdb643e00/service_bindings/4fb42865-7903-4b86-9837-7a8a9ca8036d?accepts_incomplete=true",
    "method": "PUT",
    "status": 500
  }
}

FAILED

[carolynvs]

Thanks for the heads up! I'll have minibroker look for both variants.

[carolynvs]

Hey @troytop mind taking a peek at the fix in #18 and reviewing?

I've tested locally and confirmed that the fix works with both the older and newer versions of the postgres chart.