Delete request event view

[norkans7]

After #5867

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (cda385c) to head (d396851).
Report is 289 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #5852   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          490       490           
  Lines        25251     25264   +13     
=========================================
+ Hits         25251     25264   +13     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[norkans7]

[rowanseymour]

@norkans7 @ericnewcomer maybe this url.. should be something in the contacts app? E.g.

contact/forgetme/<contact-uuid>

And then when the contact is deleted... it says contact deleted

[norkans7]

I think we use the channel event UUID since that is the one we are creating on courier at the moment we receive the callback, retrieving the contact UUID i would be a challenge I guess and an issue if we cannot find the contact

I think if we can use the contact/forgetme/<event-uuid> with the channel event UUID that would be fine so not the contact UUID.

[rowanseymour]

If we can't find the contact.. then there's no channel event and nothing to return and we noop

[norkans7]

This URL is the one we return as confirmation URL in courier
https://github.com/nyaruka/courier/pull/834/files#diff-45e8b1f3d84682ed837b92e0ff2e697b5d885ca171ecc8c3e0d766debedb7f81R258

Do you mean we need to make courier query for the contact before adding the channel event?

[rowanseymour]

Courier has to query to know if we even own the contact in question and channel events are associated with a contact.. so I think I've convinced myself that the delete status URL is just a public facing view with the contact UUID in the URL... @ericnewcomer ?

[norkans7]

I checked on the current approach to query the contact, and the logic we have is that we try to get a contact for a URN and if it does not exists we create a contact for it as that is the logic we want for messages
But we can adjust that to make the creation optional

[norkans7]

Replaced by #5928

[norkans7]

Replaced by #5928