The force field detailed in AIP-135 speaks to supporting the forced deletion of a resource and its child resources via a Standard Delete i.e. cascading delete, where without it the delete would fail as the presence of child resources prevents a parent from being deleted.
However, there are other such scenarios beyond forcing a cascading delete that the force flag should support including:
Ignoring validation wholly
Ignoring specific validations
Restricting deletion
As such, it may make sense to do one or all of the following:
Expand the accepted uses of force beyond toggling cascading deletion
Introduce the use of a force_reason or delete_behavior field in Standard Delete that is an enum providing more toggles/overrides or desired delete behavior on a per API basis
Introduce a well-known set of acceptable delete behaviors expressed as enums that APIs may introduce
noahdietz
commented
2 years ago
The
forcefield detailed in AIP-135 speaks to supporting the forced deletion of a resource and its child resources via a Standard Delete i.e. cascading delete, where without it the delete would fail as the presence of child resources prevents a parent from being deleted.However, there are other such scenarios beyond forcing a cascading delete that the
forceflag should support including:As such, it may make sense to do one or all of the following:
forcebeyond toggling cascading deletionforce_reasonordelete_behaviorfield in Standard Delete that is an enum providing more toggles/overrides or desired delete behavior on a per API basis