Closed gberche-orange closed 2 years ago
The plan_updateable should be mapped to the value of the backing service catalog
The field remains unspecified at the plan level and defaults to false at the service level, actually preventing plan upgrades.
"name": "mariadb-dedicated", "description": "MariaDB 10.3.22 databases on demand on dedicated 3 nodes galera cluster", "bindable": true, "plan_updateable": false, "instances_retrievable": false, "bindings_retrievable": false, "plans": [ { "id": "bd6616f7-5116-42b6-86f3-90d6fb88cd5a", "name": "small", "description": "Dedicated MariaDB Galera Cluster 2GB data storage with 4GB RAM/1CPU - 50 concurrent connections", "metadata": { "costs": [ { "amount": { "eur": 0 }, "unit": "Monthly" } ], "displayName": "Small Data 2GB - 4GB RAM/1CPU", "bullets": [ "2GB storage", "70 concurrent connections" ] }, "free": false, "bindable": true, "schemas": { "service_instance": {}, "service_binding": {} }, "maintenance_info": { "version": "51.2.0+osb-cmdb.1.2.0", "description": "Dashboard url with backend guid\ncf org/space annotations propagated by osb-cmdb" } },
{ "id": "1819ff29-5318-4860-bb31-d5118939e9ee", "name": "mariadb-shared", "description": "MariaDB 10.1.38 databases on demand on shared 3 nodes Galera Cluster", "bindable": true, "plan_updateable": true, "instances_retrievable": false, "bindings_retrievable": false, "plans": [ { "id": "7d1088a0-7142-483f-8865-599e59ada623", "name": "10mb", "description": "Shared MySQL/MariaDB Galera Cluster", "metadata": { "costs": [ { "amount": { "eur": 10 }, "unit": "Monthly" } ], "displayName": "10 MB", "bullets": [ "10 MB storage", "5 concurrent connections" ] }, "free": true, "bindable": true, "schemas": { "service_instance": {}, "service_binding": {} }, "maintenance_info": { "version": "1.2.0", "description": "cf org/space annotations propagated by osb-cmdb" } },
specify plan_updateable=true at the service level to turn it for all plans.
Reproduced on version 1.7.0 -->
Expected behavior
The plan_updateable should be mapped to the value of the backing service catalog
Observed behavior
The field remains unspecified at the plan level and defaults to false at the service level, actually preventing plan upgrades.
Workaround
specify plan_updateable=true at the service level to turn it for all plans.
Affected release
Reproduced on version 1.7.0 -->