-
Notifications
You must be signed in to change notification settings - Fork 59
Release 5.0.0 incompatible with PAS 2.7 #549
Comments
It looks to me like the field is still in the Edit: I misread your second part. Have you tried reaching out to Pivotal support? I went back for over a year and the field and its definition have not changed on our side, so I suspect it's a validation issue in their product. |
Update: whoops, didn't mean to close this. I'm flipping around some field values trying to make the field configurable in a way that the OpsMan UI won't outright reject the tile. Currently at attempt 2. Pivotal's tile generator still seems to have issues validating whether or not things will work ahead of time: cf-platform-eng/tile-generator#281 |
I've uploaded a possible fix as 5.0.1: https://github.com/GoogleCloudPlatform/gcp-service-broker/releases/tag/v5.0.1 The tile will still report to be 5.0.0 when installing. If it works, I can bump the version and start the release process to get it pushed to PivNet |
In 2.7 interface there is no option for cloudsql_postgres_custom_plans_0/service. With 2.6 this is a drop down which is used to select "Google CloudSQL for PostgreSQL".
Using concourse to deploy gcp service broker 5.0.0 on 2.7 I get the following error WITH cloudsql_postgres_custom_plans_0/service present
{"errors":{".properties.cloudsql_postgres_custom_plans":["Record 1: service Non-configurable properties cannot be configured."]}}
Using concourse to deploy gcp service broker 5.0.0 on 2.7 I get the following error WITHOUT cloudsql_postgres_custom_plans_0/service present
Please help to resolve this issue so we can deploy GCP Service Broker on Pivotal Cloud Foundry with OpsMan / PAS 2.7.3
The text was updated successfully, but these errors were encountered: