[Feature][Framework] Support for Project, Blueprint and Scope deletion

[keon94]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Use case

Deleting projects, blueprints and scopes is currently unsupported. This ticket will capture the R&D necessary to support this feature.

Description

There are technical challenges involved with this. The main question is, how can we purge all the domain-level data associated with a blueprint once we delete that blueprint? We need a way to perform that mapping so we know what to delete from the database.

Child issues

Scope deletion (PagerDuty + AzureDevops): #4762
UI work: #4388
Blueprint deletion PR: #5227
Project deletion PR: #5289
Scope deletion (Other plugins): #5277

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[keon94]

I'm assigning this to myself. cc @Startrekzky

[yumengwang03]

Hi @keon94 here is some additional info: in v0.18, we will (most likely, but I need to confirm in the next a few days) move data scope and transformation to be managed at the data connection level, and Blueprints will only retain its association with the data scope, meaning that adding and deleting data scope need to be done in each data connection, not from the Blueprint anymore. Deleting data scope from a Blueprint doesn't delete the data scope, but delete its association with the Blueprint. This update will be addressed in this issue: #4762

I think this might also affect Project and Blueprint deletion.

[keon94]

@yumengwang03 @Startrekzky Will it make more sense to repurpose this ticket to delete data based on scopes instead? Doing so will prevent data from getting tied the blueprint that created them
edit: nvm, I think doing that in #4762 will make more sense

[yumengwang03]

Adding the prototypes here: