WS-85: Delete capability request REST endpoint

Added new REST endpoint for deleting capability requests; requests with existing executions cannot be deleted (they must be disabled instead--like with capabilities, which will have to be implemented)

added 3 commits

• ea825e62...a80b6faa - 2 commits from branch main
• bc91f6b9 - Added new REST endpoint for deleting capability requests; requests with

Compare with previous version

added 2 commits

• 2163e382 - 1 commit from branch main
• 64b3608d - Added new REST endpoint for deleting capability requests; requests with

Compare with previous version

Am I good to merge this?

approved this merge request

this is good, but I'm not seeing where any executions are also deleted? Did I miss something?

Nathan and I talked about that one-on-one, but basically, you don't want to actually delete a request if it has executions. For the time being it's OK to just error in that case. We should probably add another disable/enable pair on this for requests that have executions, because someone just doesn't want to see it anymore.

Yeah, that makes sense. If it's done work we don't want to disappear it. As long as enable/disable and delete don't become VLASS remain two completely separate functionalities I'm good with this.

When we add versions, we need to make sure that the states all make sense and only permit things in the way we want them to. But until we have versions I see no particular reason to fuss too much about it—do it the easy wrong way rather than a harder wrong way.

yeah, we can flush out the functionality for this better when we actually have the entire structure to work with

approved this merge request

merged