Added a fix to the AWS Delete API returning 500 errors when the record doesn't exist
Merged
Added a fix to the AWS Delete API returning 500 errors when the record doesn't exist
aws-fix-delete
into
master
All threads resolved!
All threads resolved!
Type of change
-
Bug Fix -
Feature
Please provide link to gitlab issue or ADR(Architecture Decision Record)
Does this introduce a change in the core logic?
- [NO]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Does this introduce a breaking change?
- [NO]
What is the current behavior?
Storage delete on AWS will return with 500 error codes when the record doesn't exist. It will no longer do this. Also, instead of only deleting the legal tags associations with the record at time of deletion, it will delete all of the legal tag associations with that record id.
What is the new/expected behavior?
Storage delete should not return with 500 error codes when the record doesn't exist.
Have you added/updated Unit Tests and Integration Tests?
Any other useful information
Merge request reports
Activity
changed milestone to %M25 - Release 0.28
requested review from @ydzeng
assigned to @dhudsons
- Resolved by Derek Hudson
- Resolved by Derek Hudson
mentioned in commit 238f1378
Please register or sign in to reply