Backend for campaign reports
Summary
Implements #368
Created CRUD endpoints for campaign reports. They are part of a separate module called campaign-report, but the controller is under the campaign base route.
New entities:
- CampaignReport
- CampaignReportFile
Both entities support soft delete and have an owner (uploader).
Screenshot of how the new routes look like:
Todo
- [x] Endpoint for downloading files from reports
- [x] Tests for update service
- [x] Tests for update controller
- [x] Tests for delete service
- [x] Tests for delete controller
- [ ] Some manual testing of the whole process
- [ ] Manual test of s3 upload/download
- [ ] Squash migrations
@imilchev The PR check for scanning k8s manifests with mondo showed an error that you might be interested in:
Target: K8s Manifest dev-manifests
✕ Errors: rpc error: code = InvalidArgument desc = asset does not match any of the activated policies
https://github.com/podkrepi-bg/api/actions/runs/3608695854/jobs/6081448709
✅ Tests will run for this PR. Once they succeed it can be merged.
@batebobo Can you please update your PR and resolve the open discussions in order to get this PR moving? :pray:
closing in favor of https://github.com/podkrepi-bg/api/pull/453