Bulk delete of an OpenID provider (GDPR)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- backend
Research direction
Start with parent issue #41 and trace the existing single-person deletion path to find the service delete hook and the Identity, External identity, and provider models. Implement the bulk operation as one transaction, including provider-name confirmation, and run just ci; it is done when all acceptance criteria pass, including rollback if a hook fails.
Written by the indexing model from the issue text.
Description
Parent
#41
What to build
Bulk delete of an OpenID provider for GDPR requests. In one transaction, per affected Identity, it first calls the service's delete hook (delete or anonymize the Account, the same hook used for deleting a single person), then removes the External identities, the Identities and the provider. It requires typing the provider's name as confirmation.
Acceptance criteria
- Bulk delete without the matching provider name is refused and changes nothing
- The service's delete hook is called once per affected Identity
- External identities, Identities and the provider are gone afterwards
- A failing delete hook rolls the whole bulk delete back
-
just ciis green
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 10h 20m
- Merged PRs (30d)
- 36
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from myOmikron/code
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
wayfinder:task
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
wayfinder:task
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
myOmikron/code#102 · 2 comments ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 5/5 Over a week Newbie friendliness 18/100
Maintainers usually reply within 1 day
Similar issues
-
数据界面的横向滚动条缺失Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
zilliztech/attu#1037 ·
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw#181212 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apify/apify-mcp-server#1684 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Automattic/data-liberation-agent#953 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
siteboon/claudecodeui#1642 ·
Maintainers usually reply within 5 days