TSRE - Internal Support default text according to the team DoR (Definition of Ready)

01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):

@Douglas Coimbra Lopes

2 - DESCRIBE ALTERNATIVES YOU CONSIDERED:

• It is possible to delete a staging table from the Unified tenant that is part of copy data
• We should block the Unified tenant to delete any staging in the tenant that is referred on the SQL Manifest file.

03 STEPS

• Create a unified tenant
• Create a customer tenant
• Create a Carol app
• Attach the app to the Unified tenant
• Link the app with a GitHub repository
• Release and approve the app for installation
• Install the app on the customer and unified tenants
• From the UNIFIED tenant, try to drop one of the staging tables
• From the UNIFIED tenant, try to drop one of the connectors

04 - EXPECTED BEHAVIOR (LIST THE EXPECTED BEHAVIORS TO CONSIDER THIS BUG AS DONE) - ACCEPTANCE CRITERIA:

• We should block the Unified tenant from deleting any staging or connector in the tenant that is referred on the SQL Manifest file.
• We should block actions to delete data from staging tables that is referred on the SQL Manifest file.
  • Flow “Delete Staging Table Records”
  • Flows on intake to delete data (using crosswalk).
• Explorer should not allow data deletion as well.
• Only CAROL ADMIN are able to delete a staging or connector. Data deletion is blocked for everyone, including CAROL_ADMIN.