Skip to content

Make API changes to abuse api to handle cinder/DSA requirements #9304

@eviljeff

Description

@eviljeff

Depends on the model changes in #9300

We will be repurposing the existing /abuse api endpoint to also track feedback and and content violation reports we will be handing to satisfy our DSA requirements.

We need to:

  • add fields for name and email
  • call CinderAddon.report for appropriate (DSA covered) reasons
  • Cinder class will need updating to handle non-authenticated users with name and email
  • create a CinderReport instance with the job id returned from the API

┆Issue is synchronized with this Jira Task

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions