Skip to:
User impact:
User is getting no error on sending wrong/non-existing DB cluster name for creating backup.
Steps to reproduce:
Run Everest BE
Register K8 Cluster
Create backup storage location
Create backup by passing wrong db cluster name (https://jira.percona.com/browse/EVEREST-233)
Actual result:
returning 201 created
Expected result:
return error status code with error message "Could not find DB Cluster"
Tested and verified.
What's changed:
in case the DatabaseCluster with the given name does not exist, the API returns error
"DatabaseCluster '<name>' is not found"
The change is applied to the:
backups creation API
restores creation API
restores update API
I don't think this is a blocker for 0.2.0 because the UI won't allow this to happen. Can we move it to 0.3.0?
User impact:
User is getting no error on sending wrong/non-existing DB cluster name for creating backup.
Steps to reproduce:
Run Everest BE
Register K8 Cluster
Create backup storage location
Create backup by passing wrong db cluster name (https://jira.percona.com/browse/EVEREST-233)
Actual result:
returning 201 created
Expected result:
return error status code with error message "Could not find DB Cluster"