-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
0.4.0 [R5]
-
None
Currently, if an invalid value is entered through RHODA UX for CRDB serverless provisioning, a dbaasinstance is created and then after some time the backend returns an error likeĀ below:
0-invalid parameter spendLimit: strconv.ParseInt: parsing "***": invalid syntax
A validation error should be captured in the UX before the DBaasInstance CR is created so that the invalid CR does not get generated.